For Machines
One canonical commercial institution, two audiences. The same products humans read about are discoverable, payable and dependable for software: stable schemas, exact prices, one payment wallet, signed receipts and webhooks that replace polling.
Discovery, quote, payment, delivery and repeat use share one canonical catalog and one receipt chain; the payment address is advertised by the canonical x402 surface, never copied into this page.
Discovery surfaces
| Path | What it is |
|---|---|
/openapi.json | OpenAPI. Canonical HTTP contract with operation ids, schemas, errors and payment semantics. served by: machine-discovery |
/catalog.json | Catalog. The canonical product index: ids, versions, prices, schemas and availability. served by: machine-discovery |
/feed.json | Product feed. Compact versioned change feed for product availability and price changes. served by: machine-discovery |
/llms.txt | llms.txt. Curated machine-readable navigation for systems that read it; not a search lever. served by: machine-discovery |
/.well-known/agent-card.json | A2A Agent Card. Public Agent Card: endpoint, auth, capabilities and skills. served by: machine-discovery |
/mcp/server.json | MCP server metadata. MCP transport and discovery metadata for eligible tools. served by: machine-discovery |
/x402/bazaar.json | x402 Bazaar records. The discovery records published for x402 Bazaar indexes. served by: machine-discovery |
/docs/index.json | Product docs index. Stable operation ids, schemas, errors and payment semantics, one document per product. served by: machine-discovery |
/x402/ | x402. Payable endpoints; every inbound route resolves to the canonical x402 Revenue Collection Wallet. A route prefix, not a document. served by: machine-discovery |
/webhooks | Webhooks. Subscription, delivery and signature-verification contract for material events. A route prefix, not a document. served by: machine-discovery |
/.well-known/did.json | Service identity. did:web service identity and the authorized receipt signing key, when used. served by: machine-discovery |
/.well-known/security.txt | Security contact. Security contact and disclosure policy. served by: machine-discovery |
How paying works (x402)
- Every inbound commercial route resolves to the canonical x402 Revenue Collection Wallet; the address is advertised by the payable surface itself, and the wallet's private key never enters any public system.
- Retries use a logical Payment-Identifier, so a network failure or a restart cannot cause duplicate payment processing, duplicate work or duplicate delivery.
- Offers and receipts are signed with a dedicated signing key that is separate from the payment wallet; the service identity is published at /.well-known/did.json.
- Wrong chain, wrong asset, wrong address, a stale quote, a duplicate payment id or uncertain finality fails closed - the honest failure is part of the contract.
Webhooks
- Material events - changes, risk-state changes, product-version changes, completed jobs, ready data - can be delivered to you instead of polled: subscriptions are an explicit buyer action, never automatic enrolment.
- Deliveries are signed with timestamps and unique event ids, protected against replay, restricted to safe https destinations, retried with bounded backoff and moved to dead-letter receipts when they keep failing. A no-material-change window never generates a storm.
- The subscription and verification contract lives at
/webhooks.
Feeds
Humans and machines can follow Arbiter without an account:RSS,JSON Feed, and thesitemap (with the news sitemap for the last two days and the image sitemap beside it).
Human-readable docs and contact
The service pages explain each product in plain language with its exact canonical id, version and price. Integration questions, security reports and rights requests go toArbiteroperations@gmail.com; security disclosure policy is published at/.well-known/security.txt.
Every path on this page is compiled from canonical contracts by the edge machine-discovery and indexing-publisher services. This page links and explains only - it never fabricates an endpoint, a payload, a wallet address or a credential.
