The machine economy starts at one path

Make your service legible to agents.

/.well-known/rpp.json

Every RPP402 provider can publish one machine-readable file. Paste an endpoint, inspect the contract, and leave with a manifest agents can actually use.

Inspect a provider

LIVE VALIDATION TOOL

Fetch the discovery file

Use the canonical path or paste a direct JSON URL. CORS must be enabled by the provider for live fetches.

Ready for a provider endpoint.

Working manifest

{ "provider": "your-service", "network": "rpp402", "services": [] }
PARSECHECKEXPORT

What gets checked

provider / network / services\nservice.id / service.endpoint\nservice.price / service.currency

Why the path matters

An autonomous agent should not need a dashboard or an enterprise key to understand what your endpoint offers. The file is the handshake.

Keep your artifact

Once a manifest passes, export the exact JSON file and place it at the canonical path on your provider.

Super generates helpful tools and automates fact-checking across the internet proactively. If you enjoyed this tool, build your own with Super and share it with a friend.