Registry v0.1Rules in force, the list is just startingListing & enforcement rules →

Service registry

Write the rules down first; let the list grow after

Sellers list a service here. Before paying, buyer agents read the list and check price, payment rules and dispute history to decide whom to buy from. The list itself is for machines (GET /registry.json). You are on this page to find out how to get listed, what happens if a listing misbehaves, and where disputes go.

Registry status

listed services

The rules, enforcement levels, dispute ledger and machine endpoint all run today. Sellers are welcome to register.

Where the rules live

Listing & enforcement rules

Which conduct drops a listing to which level, written down so anyone can work it out.

Dispute ledger

Who has an open dispute and where it stands, in public.

The entry point for agents

A buyer agent never reads this page; it fetches the list. Each entry carries the price, payment rules, whether the service is live, and its open disputes. To check a payee before paying, call the payee decision endpoint named in the list.

GET https://oceanalt.com/registry.json

Make your service purchasable by agents

We wrap your API, content or data into an x402-payable resource, price it for machine buyers, and list it here. Buyer agents can then find you and read your payment rules.

What you get, stated plainly: one machine-readable listing and a written set of consequences if the listing misbehaves. No traffic is promised.

List your service →

A second registry: an agent's chain of accountability

The registry above answers “can this service be trusted”. At the moment of payment a buyer agent has another question: who is behind the agent on the other side, who governs its spending boundaries, and is its credential still valid.

The identity chain breaks that into five links: agent → principal → mandate → credential → wallet. Wherever the chain breaks is where accountability stops.

I am the buyer and want to check the other side

curl "https://oceanalt.com/api/registry/agent?agentId=..."

Finding nothing is normal. Publication is voluntary, and absence says nothing bad.

I am the seller and want to be findable

Tick “publish this agent's chain of accountability” in the console. What is published is posture, not values: others see that a ceiling exists, never what it is. Credentials are never published.

Open the console →

Machine-readable: /api/registry/agents