New to authority data exchange?
The idea in a minute, then the vocabulary.
Some organizations need data; others hold it. A supervisor asks a bank whether someone is a customer; a police unit asks an exchange for a wallet's history. One asks, the other answers.
Reqport is the network that carries the ask and the answer, with admission (who may participate), identity (who is asking, under what authority), and a shared rulebook (how the exchange runs). You integrate once to reach the whole network.
You are usually the responder: you receive requests addressed to your org and answer them. Request content is decrypted only inside a confidential environment (a TEE) bound to your org, and answers are structured on ISO 20022 so they interoperate with existing financial-messaging infrastructure.
Glossary
- Authority (requester)
- An organization entitled to ask for data under a legal basis, such as a police unit or a financial supervisor. It issues requests.
- Responder
- A business that holds data about a subject and answers requests, such as a bank or a crypto exchange. On Reqport, you are usually the responder.
- Subject
- The person or organization a request is about, named by one or more identifiers (an org number, a wallet address, an account).
- Actor status
- A verifiable property of the requester: the authority under which it is entitled to ask. The network checks it before a request is admitted, so asking is gated, not just answering.
- Exchange contract
- The definition of one kind of exchange: the question that may be asked and the shape of the answer. Each is a profile of an ISO 20022 base message.
- ISO 20022
- The international standard for financial messaging that banks already use. Exchange contracts extend it rather than inventing a new format, so answers interoperate.
- camt.053 / camt.053-CA
- An ISO 20022 bank statement message; camt.053-CA is the crypto-asset profile used to answer a wallet/account transaction-history request.
- DTI (ISO 24165)
- Digital Token Identifier: the canonical id for a crypto asset, resolving the 'which USDT?' problem.
- Identify-and-Refine
- A two-step pattern: first confirm whether and how a responder holds the subject, then make a narrow follow-up instead of asking for everything at once.
- Data minimization
- Only the minimal answer is mandatory (a yes/no, an identifier); more is disclosed step by step, so the total data shared is the least that answers the question.
- Human-in-the-loop
- A response can be held for a person to approve before it leaves the responding organization.
- ARM
- Authority Request Management: one family of authority-to-company exchanges. Members are the business-relationship check, free-text (a note and attachments), and structured requests (transaction history, KYC, relationship-typed follow-ups).
- authorityArmEnabled
- The per-organisation flag that turns structured ARM create and respond on. While it is off, free-text stays the primary path.
- TEE
- Trusted Execution Environment: a confidential compute enclave. Request content is decrypted only inside a TEE bound to your organization.
- Market overlay
- Market-specific names, aliases, or rules layered additively onto a contract (keyed by country), so the core stays language- and jurisdiction-neutral.
- Sandbox
- A safe environment seeded with synthetic requests. Build and test the full loop there before switching to prod.
- qp / the CLI
- The Reqport command-line tool (@reqport/cli, binary qp). Discover, read, and answer requests from a terminal or an AI agent.
- MCP
- Model Context Protocol. qp mcp runs a stdio MCP server so an AI agent can drive the network as tools, with the exchange contracts available as context.