RAVEN. / request access

Request access

Tell us what you're building and name one token. We will run it through the live verifier and reply with a sample signed receipt — findings, coverage gaps, rules and observation data, and signed verification fields — plus an API key if it is a fit.

What happens after you submit. A human — not an autoresponder — reviews every request and replies by email within 48 hours, with your sample signed receipt and, if it is a fit, an API key with docs and a sample curl.
What we need. Only what this form asks for — above all, the decision the evidence would support.
What we will never ask for. API keys, seed phrases, wallet or signing material, or any secret — not in this form, not later.
Acknowledgement. Submitting shows a confirmation page restating these steps; the reply email is the only further contact — no newsletter, no list.
Paste whatever you have: the token's mint address, its name or ticker, or just a DexScreener/Birdeye link. We'll find it and run the check.
What we should call you in the reply. First name or a handle is fine.
Where we send your signed receipt. Never shared, never published.
One line about what you're building or doing — a trading bot, an AI agent, a wallet, a community you moderate. "Just checking a token before I buy" is a perfectly good answer.
Helps us reply at the right level — beginner answers get plain language, developer answers get curl and config.
Where the receipt fits in your flow. Examples: "check a token before I ape", "my agent verifies every token before trading", "screen launches for my group".
The yes/no moment where the evidence matters. This is the single most useful thing you can tell us.
Missing evidence you care about most Raven lists what it has NOT checked in every receipt. Which gap would you most want closed?
Raven works without any storage — receipts are yours to keep wherever you like. This just tells us whether to prioritize storage guidance and adapters. See /receipt-storage.html.
How you'd rather call Raven. Hosted = we run it, you get signed receipts by key. ACP = your agent pays 0.1 USDC per job, no key. MCP = run it locally for free. "Unsure" is fine — we'll recommend one.
A rough guess at how many token checks you'd run per day once you have a key. It only helps us size your rate limit — guessing low or high is fine.
An advanced extra check: how concentrated the token's holders are — with known pool and venue wallets factored out, so a liquidity pool doesn't get mistaken for one giant whale.

Never include API keys, seed phrases, or wallet/private material in your request — we will never ask for them. We'll run your token and reply with a signed receipt.

Raven Scout — how to read what you'll get back

A current receipt-v1 returns signed evidence: findings, coverageGaps, and rulesVersion; observation and freshness data in slot, timestamp, and maxAgeSeconds; and verification fields payloadHash, receiptId, signerPublicKey, and signature.

When something cannot be checked, the receipt says what was and was not observed through explicit findings and coverage gaps. If the evidence required to issue a receipt cannot be established, the service refuses instead of returning a silent pass.

Raven never says "safe". If coverage gaps remain, the honest answer is: not enough evidence for a full pass — and the receipt will list exactly which gaps those are.