Contributing to the Open 402 Directory

March 23, 2026 · View on GitHub

Thank you for your interest in contributing to the Open 402 Directory. This registry is a public good — every domain you add makes the 402 ecosystem more discoverable for everyone.

Ways to contribute

1. Add a domain

The most common contribution. If you know of an API that accepts HTTP 402 payments, add it.

Three ways to add a domain:

  • Web form — Submit instantly at open402.directory
  • GitHub Issue — Use the Add a domain template
  • Pull Request — Fork and edit domains.txt directly (below)

Before submitting via PR, check that:

  • The domain is a real, publicly accessible API (not a test or localhost URL)
  • The domain isn't already in registry/domains.txt
  • If marking as verified, the domain serves a valid agent.json at /.well-known/agent.json

How to submit:

  1. Fork this repository
  2. Add a line to registry/domains.txt following the format:
yourdomain.com | verified | submit | YYYY-MM-DD

or, if the domain doesn't host agent.json yet:

yourdomain.com | unclaimed | submit | YYYY-MM-DD
  1. Open a pull request using the provided template

Source values:

ValueWhen to use
selfYou own or operate the domain
submitYou're submitting someone else's domain via PR or the web form
402indexSeeded from the 402index.io aggregator
onchain-x402Auto-discovered from on-chain x402 payment activity

When in doubt, use submit.

One domain per PR. This keeps the review process fast and the git history clean.

2. Report a problem

  • Dead domain — The API no longer exists or returns errors. Open an issue.
  • Malicious domain — The listing is spam, phishing, or serving harmful content. Open an issue with urgency noted.
  • Incorrect status — A domain is marked unclaimed but actually hosts agent.json, or vice versa. Open an issue.

3. Improve documentation

Found a typo or unclear section in the README? PRs welcome. No issue required for documentation fixes.

What we accept

SubmissionAccepted?
Real API domain that accepts 402 paymentsYes
Domain that hosts agent.jsonYes
Well-known API provider (OpenAI, Stripe, etc.) as unclaimedYes
Domain you own and want to listYes
Test/staging domains (localhost, .local, .test, .example)No
Domains that don't serve an APINo
Duplicate of an existing entryNo
Bulk additions (100+ domains in one PR)Contact maintainers first

What we don't accept

  • Modifications to snapshot.json — This file is auto-generated. Changes will be overwritten on the next crawl. If you need to fix metadata, update the agent.json on the domain itself.
  • Removal of domains without justification — Domains are removed only if they are confirmed dead (30+ days unreachable), malicious, or at the owner's request.
  • Changes to the domains.txt format — The format is standardized. Propose format changes via an issue first.

Pull request guidelines

  1. Use the PR template — It exists for a reason. Fill out every field.
  2. One domain per PR — Makes review fast and reverts clean.
  3. Use today's date — The added_date field should be the date of your PR, not a past date.
  4. Alphabetical insertion is not required — Append to the end of the file. The nightly crawl sorts the registry.
  5. Don't modify snapshot.json — It's auto-generated.

Review process

  • PRs that add a verified domain with a valid agent.json are typically merged within 24 hours.
  • PRs that add an unclaimed domain are reviewed manually to prevent spam. Allow 48 hours.
  • If your PR is not reviewed within 72 hours, leave a comment — we may have missed it.

Code of Conduct

This project follows the Contributor Covenant Code of Conduct. By participating, you agree to uphold these standards.

Questions?