Documentation / Tools 1.3.0
Generate, publish, and connect.
Create files from your website, check them after publishing, and integrate action recovery when your service supports it.
Generate from your website
Scan public documentation, APIs, llms.txt, and agent connections to generate JSON, TXT, README, and listing text.
Read the guide Site formatSite Profile 1.1
Structured public resources, API operation indexes, and matching TXT files.
Read the guide PublishingAudit your files
Check the published profile, TXT, and README, with clear results and steps to fix missing or incorrect files.
Read the guide OverviewCompare the formats
Understand how Agentic fits alongside documentation, APIs, and agent tools.
Read the guide PublicationTXT, README, and listing text
TXT 1.2 project references, automatic README and listing copy, and complete publication checks.
Read the guide ProtocolsMCP, WebMCP, A2A, and Agent Auth
Connect MCP tools, WebMCP pages, A2A, and Agent Auth through their documented endpoints.
Read the guide Start hereQuick start
Run the ticket service, lose a response, and recover the original result.
Read the guide ReferenceSpecification
Versioned fields, client and service requirements, and the supported OpenAPI binding.
Read the guide IntegrationIntegration guide
Connect an existing API or agent runtime. Keep authorization and recovery boundaries explicit.
Read the guide TestingCompatibility runner
Test a separately implemented client through a small process interface and publish evidence.
Read the guide ProtocolConformance
Understand structural, binding, and behavior checks—and what the tests do not establish.
Read the guide OperationsSecurity and limits
Approved origins, private ledgers, tracking windows, credentials, and unresolved outcomes.
Read the guideQuick start
Requires Node 24 and Python 3.11 or later. This example runs locally and creates synthetic tickets.
git clone https://github.com/sam1siam/agentic.git
cd agentic
npm ci
python -m pip install -r reference/python/requirements.txt
python reference/service/server.py --fault response-lostIn a second terminal, from the same repository:
npm run client -- http://127.0.0.1:4318 example-001 "Example ticket"
# Repeat the exact command to return the saved receipt.The service commits the ticket and drops its first reply. The client checks the saved request, reads the original ticket, and emits a receipt with outcome: succeeded. Keep the same request ID and input when resuming.
Frequently asked questions
Is Agentic available for production use?
Yes. Tools 1.3.0 support Site Profile 1.1.0 and Action Profile 1.0.0. Generate a site profile from public sources. If you implement action recovery, also validate its bindings and test the service behavior.
Does stable release mean every agent supports it?
No. Stable versioning defines the published contract. Clients must implement that contract, and a release does not imply universal support, external certification, or standards-body endorsement.
Will agents discover agentic.json automatically?
Only clients that implement this convention can use it. Pass the profile URL explicitly to your supporting client. Publishing the file alone does not add support to an agent.
What does a service need?
A public website is enough for a site profile. An action contract additionally requires submission, request-status, and resource reads plus durable request tracking and idempotency.
Does Agentic require other agent files?
No. Use agentic.json and its generated agentic.txt index. llms.txt remains an optional documentation source. Protocol links use their own contracts and authorization.
Does the profile make an API safe to call?
No. The agent host still authorizes the action, approves destinations, protects credentials, and isolates ledgers. A publisher’s description is untrusted data.
Does it guarantee exactly-once execution?
No. The service must enforce idempotency. The client avoids automatic repeat writes and uses authoritative status plus evidence. Unresolved cases remain pending or unknown.
What happens when the request window expires?
The client preserves unknown and hands off to its host. It must not assume the action failed or create a fresh request automatically.
Can my team use it without publishing private data?
Yes. Run the local example or hosted sandbox. Share redacted results and aggregate counts; do not upload tokens, customer inputs, private receipts, or ledgers.