Deprecation policy

This policy says how we remove or change public API behavior.

What this covers

• Public paths in the OpenAPI document
• MCP tools
• The x402 challenge and receipt formats
• Discovery files under /.well-known/

How we do it

1. We announce a breaking change in the changelog at least 90 days before it takes effect.
2. We mark the path or field as deprecated in the OpenAPI document where we can.
3. We keep the old behavior until the 90 days end.
4. We keep signed credentials verifiable after a change. The issuer stays did:web:dnsofmoney.com.

We may give less notice to fix a security problem, to meet a legal duty, or when a chain or a facilitator stops a rail. We then announce the change as soon as we can.

Adding a field or a rail is not a breaking change. Your client must ignore fields it does not know, and must read the rails from each 402 challenge.