Credential and tenant model
Production integration would need explicit onboarding, scoped credentials, runtime authorization, audit boundaries, and revocation behavior.
Public integration status
Integration status.
AgentReceipts is in RC1 public discovery and static sandbox mode. The public site explains the pattern, exposes public-safe examples, and helps developers inspect metadata-only discovery contracts and local or manual workflow patterns.
Current status
Discoverable static public surface
Current status: RC1 public discovery and static sandbox. AgentReceipts is published as public-safe examples, metadata-only discovery contracts, and local or manual workflow patterns. It is not a production API, credentialed runtime, payment service, or legal authority layer.
Not live yet
Runtime and commercial controls
There is no public credential issuance, no public runtime authorization, no live Signal Core intake, no public MCP Gateway access, no payment execution, no settlement, no production SLA, no legal validity guarantee, and no tenant onboarding.
What can be tested now
Use public files and static examples only.
Read discovery
llms.txt and .well-known files
Try sandbox/sandbox/
Verify sample/verify/sample-agentic-402/
Inspect workflowlocal GitHub Actions patterns
You can read llms.txt, inspect .well-known files, use the static sandbox, verify the sample receipt, inspect public schemas/examples, and generate or inspect local GitHub Actions workflow patterns.
Agentic 402 clarification
A recognizable sandbox pattern, not payment execution.
What Agentic 402 means here
It is a sandbox entitlement and receipt example. It uses a 402-style flow as a recognizable test pattern for an agent blocked on a required condition, then allowed to continue inside the sample boundary.
What Agentic 402 does not mean
It does not prove real payment, settlement, external execution, or independent identity assurance. The public receipt only demonstrates an internally consistent static example.
Public files interpretation
Public discovery projections are descriptive.
llms.txt, robots.txt, sitemap.xml, and .well-known files are public discovery projections. They help agents and developers understand the pattern. They do not grant authority, credentials, runtime access, or permission to act.