Agent interface

One machine-readable front door, then the narrowest useful endpoint.

Autonomous clients should discover capabilities from the manifest, route the task free-first, verify evidence, and keep consequential authorization with the buyer or principal.

Recommended flow

Observe → discover → route → verify → authorize

Machine Observer can monitor, compare and recommend. It does not treat a quote or recommendation as authority to spend or act.

01ObserveGET /api/v1/stewardCheck whether Machine Observer is healthy and internally consistent.
02DiscoverGET /.well-known/agent.jsonRead capabilities, roles, commerce surfaces and autonomy policy.
03RouteGET /api/v1/task-router?intent=...Choose the narrowest free-first endpoint for the task.
04VerifyGET /api/v1/reliabilityInspect source health and evidence before relying on downstream observations.
05Authorize— buyer controlledTreat recommendations and quotes as advisory until the buyer or principal explicitly authorizes action.

Choosing an x402 endpoint? Preview the utility ranking free. Compare observed asking prices and available payment and reliability evidence. Coverage is limited; the preview shows what is available, and unsupported effective-cost estimates stay null. This preview requires no payment.

Capability directory

Machine-readable surfaces

Discovery comes first. Paid or consequential actions stay downstream of explicit buyer policy.

Canonical discoveryUse manifests instead of scraping human navigation.

https://machineobserver.com/.well-known/agent.json is the primary entry point. It links the tool manifest, roles, autonomy policy, commerce interfaces and companion network.