VEY1 API
Forensic crypto project due diligence. One endpoint, two modes: a free demo
(rate-limited to 1 call per 30s) for trying things out, and the production
POST /v1/audit endpoint that's paywalled via the
x402 protocol on X Layer
(1.5 USDT0 per audit).
- Your agent sends a request to
POST /v1/auditwithout a payment header. - VEY1 returns
HTTP 402with aPAYMENT-REQUIREDresponse header containing the base64-encoded x402 challenge (the amount, network, receiving wallet, and asset contract). - Your agent signs the challenge with its Agentic Wallet (EIP-3009 / EIP-712 signature on the USDT0 contract).
- Your agent re-sends the same request, this time with the signed payment in the
X-PAYMENTheader. - VEY1 verifies the payment against the OKX facilitator, then runs the audit and returns the result + PDF link.
Free demo
Request body
{
"query": "SushiSwap" // OR use a preset via "target": "uniswap" | "hyperliquid" | "safemoon"
}
Response (200 OK)
{
"reportId": "TL-2026-07-15-XXXX",
"project": "SushiSwap",
"riskScore": 50,
"recommendation": "CAUTION",
"reasoning": "The Uniswap project has a neutral risk profile...",
"flags": [{ "color": "YELLOW", "category": "DATA_GAP", "message": "..." }],
"comparableProjects": [{ "name": "Uniswap", "status": "ACTIVE" }],
"pdf": { "url": "https://vey1.xyz/reports/TL-2026-07-15-XXXX.pdf", "pageCount": 8 },
"html": { "url": "https://vey1.xyz/reports/TL-2026-07-15-XXXX.html" },
"durationMs": 4250
}
Try it
curl -X POST https://vey1.xyz/v1/demo \
-H "content-type: application/json" \
-d '{"query": "SushiSwap"}'
Paid audit (x402)
eip155:196). Your Agentic Wallet signs the payment
automatically when it sees the 402 response.
Step 1 — Make a request without payment
curl -i -X POST https://vey1.xyz/v1/audit \
-H "content-type: application/json" \
-d '{"query": "Uniswap"}'
Step 2 — Receive the 402 challenge
HTTP/2 402
content-type: application/json
payment-required: eyJ4NDAyVmVyc2lvbiI6MiwicmVzb3VyY2UiOnsidXJsIjoi...
x-payment-required: eyJ4NDAyVmVyc2lvbiI6MiwicmVzb3VyY2UiOnsidXJsIjoi...
{
"x402Version": 2,
"resource": {
"url": "https://vey1.xyz/v1/audit",
"description": "VEY1 forensic project audit — returns a 12-18 page PDF",
"mimeType": "application/json"
},
"accepted": {
"scheme": "exact",
"network": "eip155:196",
"maxAmountRequired": "1500000",
"payTo": "0x72233b78747765244855dd27180bbed9c0245f96",
"maxTimeoutSeconds": 300,
"asset": "0x779ded0c9e1022225f8e0630b35a9b54be713736",
"extra": { "name": "USD₮0", "version": "1" }
}
}
Step 3 — Your agent signs + retries
Your Agentic Wallet (e.g. via the onchainos CLI or the OKX Pay SDK) signs the maxAmountRequired USDT0 transfer authorization (EIP-3009 TransferWithAuthorization), wraps the signature in a base64-encoded JSON payload, and re-sends the same request with that payload in the X-PAYMENT header.
Step 4 — Receive the audit
Once the facilitator verifies the payment on-chain, the same JSON response as the free demo is returned, plus the signed X-PAYMENT-RESPONSE header with the settlement receipt.
Try it with the onchainos CLI
curl -i -X POST https://vey1.xyz/v1/audit \
-H "content-type: application/json" \
-d '{"query": "Uniswap"}' 2>&1 | head -20
# → see the 402 challenge and the PAYMENT-REQUIRED header
Service info
curl https://vey1.xyz/v1/info
Report files
Error codes
| Status | When |
|---|---|
200 | Success. Report is in the response body + pdf.url / html.url. |
400 | Missing or malformed query field. |
402 | x402 challenge. Send the signed payment header to retry. |
429 | Demo rate limit (1 call per 30s per IP). |
500 | Audit pipeline error. Inspect the error field for details. |
What the audit contains
Every report is a 12-18 page PDF covering:
- Executive summary — risk score (0-100), recommendation, reasoning, top flags.
- Project profile — name, ticker, contract, chain, social links, identity confidence.
- On-chain audit — every project-controlled wallet, its funding source, first-seen date, counterparty graph.
- OnchainOS real-time evidence — security scan, holder cluster analysis, deployer's other tokens, smart money signals, social sentiment, cited news, deployer wallet PnL. Every data point is cited to the specific OKX OnchainOS skill that returned it (
okx-security,okx-dex-trenches,okx-dex-signal,okx-dex-social,okx-dex-token,okx-dex-market). - Team dossiers — for every identified team member: identity verification, public social footprint, past project associations, personal on-chain wallets, scam database cross-reference.
- Risk synthesis — the LLM's evidence-based narrative with explicit
Per okx-<skill>:citations. - Comparable projects — 3-5 historical analogues with status (ACTIVE / RUGGED / ABANDONED / ACQUIRED).
- Final recommendation —
PROCEED/PROCEED_WITH_MONITORING/CAUTION/AVOIDwith next steps. - Methodology & data sources — what data we used, what we couldn't, the data confidence score.