Verify an investor from any agent.
ChatGPT, Claude, an investor portal's onboarding agent — anything that speaks MCP or HTTP can start a verification, hand over the documents and fetch the letter. One step stays with the investor: signing, the identity check and payment, on one page, in about a minute.
Connect over MCP
The endpoint is Streamable HTTP at https://mcp.roji.ai, authenticated with OAuth 2.1 and dynamic client registration. Your client discovers the authorization server and drives the sign-in; the investor approves the connection once.
claude mcp add --transport http roji https://mcp.roji.ai
The investor's tools
find_verification_program— find an offering's program by its code, or by the issuer's domain (the_rojiDNS record): offering, price, methods.start_verification— open a case for the signed-in investor, for a program or on their own.get_verification_requirements— the checklist for the method: what is done, what is missing and why, and whether the case is ready to sign.set_verification_method— income, joint income, net worth, or a Series 7, 65 or 82 licence.upload_verification_document— send a document against a checklist item; the reply says what was read and what is still missing.get_signing_link— the one link the investor opens to sign, verify their identity and pay.get_verification_status— the case's state, any item returned with its reason, and the expected time.get_verification_letter— the letter PDF and its lookup link, once issued.share_verification_letter— share a valid letter with another issuer's offering, free.
Issuer-side tools for platform agents: create_verification_program, invite_investor_to_verify, list_program_verifications.
A whole case, from an agent
User Get me verified as accredited for Acme Fund III. My W-2s are in my Drive.
Agent → find_verification_program(domain: "acmecapital.com")
→ start_verification(program_code: "acme-iii")
→ get_verification_requirements(case) # income: two W-2s
→ upload_verification_document(case, W-2 2024)
→ upload_verification_document(case, W-2 2025)
→ get_signing_link(case)
Agent Both W-2s are in and read. Sign and pay here, about a minute:
https://roji.ai/s/7hq2 — I'll tell you when the letter is issued.
The human moment
Only the investor can sign, verify their identity and pay. When get_verification_requirements says the case is ready to sign, call get_signing_link and give the URL to the investor. Do not try to open or complete it yourself. Then poll get_verification_status no more than once a minute, or tell the investor they will get an email when the letter is issued.
A licensed attorney or CPA reviews the case and signs the letter, usually the next business day. The agent never states that the investor is or is not accredited.
Over REST
Every MCP tool is a thin layer over https://api.roji.ai. The same calls, for an integration that would rather speak HTTP:
GET /public/verification-programs/{code} the program behind a button
POST /verification-cases open a case
GET /verification-cases/{caseId} checklist, state, what is missing
PATCH /verification-cases/{caseId} set the method
POST /verification-cases/{caseId}/documents upload a document
POST /verification-cases/{caseId}/signing-link the investor's signing link
GET /verification-cases/{caseId}/letter the letter and its lookup link
POST /verification-cases/{caseId}/share share a valid letter
POST /verification-programs create a program (issuer)
POST /verification-programs/{id}/invites send an investor a pre-filled link
GET /verification-programs/{id}/cases status per investor, never evidence
GET /verification-programs/{id}/export the offering-file export
GET /public/letters/{lookupCode} public letter lookup
Events go to the issuer's webhook endpoints, signed: verification.started, verification.submitted, verification.item_returned, verification.letter_issued, verification.unable_to_verify, verification.expiring, verification.expired, verification.letter_shared. Payloads carry the case, your own investor reference, the state and the lookup link — never documents or the figures in them.
Built for agents
OAuth 2.1
Dynamic client registration and PKCE. A person authorises every agent; there is no client-credentials grant.
One human step
Everything is callable except signing, identity and payment — handed over as a single link.
Webhooks
HMAC-signed events for every state change, delivered to the issuer that owns the program.
Markdown twins
Every page, and every program's hosted page, has a markdown version an agent can read. Start at /llms.txt.
Questions from agent builders
For builders
Verify an investor from your agent.
MCP at mcp.roji.ai, REST at api.roji.ai — the same case either way.