For developers & partners
Build on the Reqport network.
Receive, verify, and respond to law enforcement data requests from your own systems. Use the Reqport API, CLI, or MCP server to pull verified requests into your workflow and send responses, with request contents encrypted end to end.
Start your way
The same responder loop (discover, read, answer) works from the command line, from your AI agent over MCP, or handed to a coding agent as a skill. Test everything against sandbox first.
Command line
Install the CLI, sign in, and answer a request in a handful of commands. The binary is qp.
npx @reqport/cli@latestthen: qp login → qp requests list → qp respond
From your AI agent
Run qp mcp to start a stdio MCP server that exposes the same operations as tools, with the exchange contracts available as context.
qp mcppoint any MCP client at it, like Claude Code or Cursor
Agent skill
Hand your coding agent the Reqport responder skill. It installs the CLI, points at sandbox, and implements a responder integration end to end.
Give it to your agentResources
Quickstart
Zero to a working responder integration: mint a sandbox key, discover a request, answer it.
Exchange contracts
The catalogue of exchange types on the network. Each one is built on ISO 20022, versioned, and referenceable.
How exchanges work
The request/response envelope and the named patterns: Identify-and-Refine, data minimization, human-in-the-loop release.
Connect
Join the network, get admitted, and mint per-environment API keys from the console.
ARM
The authority-request family: a business-relationship check, free-text, and structured requests, and when each one is available.
Explore by exchange type
Structured exchanges are versioned contracts on an ISO 20022 base: structure in the clear, payload sealed to the two parties. Free-text is the ARM member with no request schema.
Business-relationship check
Is this subject your customer? A yes/no answer, with accounts where applicable.
Free-text
A note and attachments: the ARM family member used when no structured profile fits.
Crypto transaction history
A camt.053-CA statement for an address or account, answered from the responder's own records.
Fraud incident response
Case-based FI↔FI exchange: a fraud notice, a refund instruction, and an identity request, in one thread.
KYC / CDD
Customer due-diligence identity exchange, built on a shared IVMS101-aligned identity core.
Learn the concepts
Anyone can define a data format. What makes an exchange work between organizations is everything around it: who's allowed in, the order things happen in, and a place the rules live. Reqport operates those four things.
The network
The connected set of authorities and businesses that exchange data with each other. You integrate once to reach the whole network, not one counterparty at a time.
The doorman
Admission, identity, and authority status. Who is entitled to ask, and who must answer, is verified, not assumed, before any exchange is admitted.
The rulebook
The workflows and exchange patterns that define how a request is made and answered. They are versioned, referenceable, and maintained so every participant stays in step.
The registry
The canonical directory of exchange contracts and their versions that Reqport operates. It is the single reference every participant points at.
Ready to join the network?
Get your organization admitted, then mint per-environment API keys and enable the exchanges you need. Start in sandbox, then move to production.