com.publicdomainrelay.temp.market.bidderDiscovery

Published by a bidder in its own repo to announce availability. The bidder periodically updates `updatedAt` to signal liveness. The market registry polls this record to decide whether the bidder is still active.

Details · record, key tid
Kindrecord
Record keytid
Authoritymarket.temp.publicdomainrelay.com
Indexed

Record

record · key tid

Properties

appliesTo

requiredarray

Payload NSIDs this bidder handles (e.g. com.publicdomainrelay.temp.compute.vm).

  • minLength: 1
itemsstring · nsid

createdAt

requiredstring · datetime

endpointUrl

requiredstring

Service DID ref (e.g. did:web:HOST#pdr_temp_market) where submitRfp calls should be routed.

updatedAt

requiredstring · datetime

ISO 8601 timestamp of the last liveness update. The bidder updates this periodically; the registry treats a record as stale when updatedAt is older than a configured threshold (default 5 minutes).

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • An index entry in the market registry's repo tracking a registered bidder. The registry creates one entry per (bidderDid, payloadNsid) pair when a bidder calls registerBidder. Liveness is determined by polling the bidder's own bidderDiscovery record — this index entry carries no heartbeat timestamps. When a bidder goes stale the registry deletes its index entries.

  • Declares that a bidder is willing to submit bids for RFPs whose payload NSID is in appliesTo. The bidder's market service DID reference (for submitRfp via PDS proxying) is given by endpointUrl.

  • Register a bidder with the market registry. Called by bidders after they publish a bidderDiscovery record in their own repo and connect to the relay. The registry verifies the caller's service-auth JWT issuer matches the bidderDid, then indexes the bidder so it appears in listBidders queries. Liveness is determined by the registry polling the bidder's bidderDiscovery record — there is no separate heartbeat procedure.

  • Top-level Request For Proposal (RFP). Envelope that strongRefs a domain-specific payload (e.g. compute.vm).

  • List of AT Protocol relay URLs that the record owner recommends for market discovery. Requesters read this record via autoDiscoverRelayUrls to find relays to query for bidder offerings.