AP
Agent Provider Depot
Opinionated picks for agents
OpenAPI

Claim your provider listing

Providers can prove they control their domain and publish a signed price feed. Depot checks every feed price against the provider's own public pricing page before accepting it.

Claiming never affects rank. Claiming a listing or submitting a price feed never affects picks, scores, ranks or result order. Unclaimed providers are ranked by the same rules. No payment, partnership or feed changes a pick.

Status on this deployment: not open yet (provider_claims_need_a_remote_store). POST /api/providers/claim answers 503 until a store is configured.

1. Verify your domain

Start a claim with POST /api/providers/claim and the body {"action":"start","providerId":"<id>","domain":"<domain>"}. The domain must be the host of your listing's website or of one of your official pricing pages in the catalog (see GET /api/providers/claim?provider=<id>). Shared hosts (GitHub, docs platforms and the like) and any other domain go through a manual review instead. Publish the token you get back in one of two places:

  • DNS TXT: _depot-verify.<domain> with the value depot-verify=<token>
  • Well-known file: https://<domain>/.well-known/depot-provider.json, matching provider-well-known. It holds the token and your Ed25519 public signing keys.

Then send {"action":"verify","providerId":"<id>","domain":"<domain>"}. Depot looks up the TXT record and fetches the well-known file over HTTPS, without following redirects. It never contacts any host other than the claimed domain.

2. Submit a signed price feed

Build a provider-price-feed document (Depot Open Pricing & Outcome Schema v0.1). Sign the canonical JSON of the feed without its signature member (RFC 8785 JCS rules) with Ed25519, and send {"action":"feed","feed":{...}}. Depot:

  1. validates the feed against the schema, and checks that every sourceUrl is on the verified domain;
  2. requires a verified claim for that provider and domain, and a sequence higher than the last accepted one (no replays);
  3. verifies the signature with a key it fetches from your domain. Keys sent in the request are never trusted;
  4. cross-checks every price against its public page: the amount and the SKU name must both appear there. A price that only appears in the feed is recorded as not_found_on_public_page and is not used;
  5. queues matching prices for a reviewed re-price, the same path as a correction. The catalog is never edited automatically, and history stays append-only.

What claiming does and does not do

  • Does: faster, source-backed price corrections, and a record that your prices were confirmed against your own page.
  • Does not: change a pick, a score, a rank, a leaderboard position or result order. It does not hide competitors or remove history. Unclaimed providers are ranked by exactly the same rules.

Full spec: research/PROVIDER-PROGRAM.md. Machine-readable: /api/providers/claim. Neutrality charter: research/STRATEGY.md §6.