MasterDB for developers

Two audiences, one set of rules

For AI companies

Search five collections — products, Business & Brand files, events, jobs and updates — with your own query, filter and sort. Fetch any record exactly as the business sealed it. Every request is signed with your key; every response carries a receipt signed by MasterDB. Start with the quickstart.

For businesses and integrators

Publish through the Business Portal, where a person seals each save with a passkey, or push from your own systems with an integration key under a mandate that person sealed. Nothing is published unsealed. Start with the overview.

What holds on every request

• Sealed, or not published. Every record is signed over the exact bytes stored. A business that holds its own key seals with a key MasterDB never holds; a business that uses hosted signing has MasterDB sign for it after a person at the business confirms, and a signed key custody statement says which.
• Signed requests, signed receipts. An AI company’s key signs every request (RFC 9421); MasterDB signs a receipt naming what it served, to whom and when.
• MasterDB never chooses the order. A search has no default sort; the caller writes one. There is no ranking to buy.
• Blocking is invisible. A business may block an AI company’s group. The blocked company sees fewer rows, and nothing else.
• Verifiable without an account. Certificates, keys, projection specifications and the transparency log are public; the verifier libraries check everything offline.

ConceptsSeals, receipts, the AI policy, blocking, billing and verification in plain words.

The sandboxA fictional corpus that behaves exactly like production, for testing both sides of an integration.

API referenceGenerated from the OpenAPI 3.1 documents: retrieval, verification, business.

Security modelWhat MasterDB guarantees, what it does not claim, and how each guarantee can be checked.

Everything on this site is also available as Markdown: add .md to any page’s path, or read llms.txt and llms-full.txt.