For suppliers
Publish once. Let any agent discover, invoke and inspect it.
A Tracert listing is not a company profile — it’s a callable capability: one bounded promise with a clear contract and an inspectable execution trail. Agents select services on structured facts, not marketing pages.
No wallet, no listing fee, no payment integration required. A free capability is published with nothing but a pull request. Monetization is an optional upgrade, never a gate.
The onboarding ladder
Take the smallest step that fits your service; each level is optional.
| Level | Your work | What you get |
|---|---|---|
| Listed | Submit and maintain a manifest. | Discovery in the index, MCP router and capability pages; schema validation; a stable capability ID. |
| Routed | Provide API details or approve an adapter. | The gateway normalizes invocation, observes outcomes and issues TRACE Receipts for you. |
| Native | Expose MCP / A2A / machine-payment interfaces. | Agents route to you directly when their policy allows; your capability identity and history carry over. |
What a strong capability looks like
- A bounded promise. “Turn an image into a colouring page”, not “AI image suite”. One promise per manifest — agents match intents, not brands.
- A deterministic contract. JSON Schemas for input and output, media types, size limits, and error codes an agent can act on.
- Declared data handling. Retention, training use, regions, subprocessors. Absence is never treated as a safe default — declaring honestly is a selection advantage.
- Evidence. Public examples, test vectors, recent executions. Fresh evidence beats static claims in every agent’s ranking.
- Honest provenance. Who operates the service, who operates the adapter, and whether the integration is official.
How to publish today
- Author a manifest against the TRACE Manifest v0.1 schema. The worked example: ai-directory.publish-listing.
- Validate locally — the registry ships an
npm run validatethat checks schema conformance, ID discipline, schema references and placeholder rules. - Open a pull request to the public registry: github.com/tracert-network/tracert. Validation re-runs in CI; the merged PR is your durable public record.
The registry is public and version-controlled today at github.com/tracert-network/tracert — the manifest format is stable to author against now, and a merged pull request is the real onboarding path.
Pricing a capability (optional)
Declare payment_offers in the manifest — MPP, x402, prepaid balance, BYOK, subscription or invoice — and the router negotiates a method the buyer can actually present. Quotes are exact and expire; a service can never silently charge a different amount. Paid routing goes live with the payment adapter phase; free capabilities route already.
The rules that protect everyone
- Stable IDs: your capability ID survives interface and provider migrations.
- Public by default: manifests, changes and removals are inspectable history.
- No pay-to-rank, no sponsored placement — ranking reasons stay inspectable.
- Wrapped services must label the underlying provider and adapter operator — technical compatibility is never presented as endorsement.