Quickstart
Get validated web evidence from multiple sources in minutes.
1Send a request
2Receive HTTP 402
3Get your evidence
4Integrate and scale
After HTTP 402, an x402-enabled client authorizes payment. Veyrly then runs the provider, validates the evidence, settles only after validation succeeds, and returns the result.
1. API endpoint
POST
https://api.veyrly.com/v1/evidence2. Request and response
Example request
curl -X POST https://api.veyrly.com/v1/evidence \
-H "Content-Type: application/json" \
-H "Idempotency-Key: YOUR_UNIQUE_KEY" \
-d '{
"query": "What is the purpose of robots.txt?",
"max_sources": 5
}'Example response (shortened)
{
"status": "fulfilled",
"query": "What is the purpose of robots.txt?",
"answer": "The Robots Exclusion Protocol lets site owners communicate crawler access preferences.",
"sources": [
{
"title": "RFC 9309: Robots Exclusion Protocol",
"url": "https://www.rfc-editor.org/rfc/rfc9309.html",
"snippet": "This document specifies the Robots Exclusion Protocol.",
"published_at": "2022-09-01T00:00:00Z",
"updated_at": null
}
],
"freshness": { "required": false, "satisfied": true, "newest_timestamp": null },
"evidence": { "source_count": 5, "distinct_source_count": 4, "validated": true },
"fulfilled_at": "2026-09-01T21:11:48.428Z",
"request_id": "78390ac9-ff82-459e-a7f0-2ee63ce2553c"
}Endpoint details
| Method | POST |
|---|---|
| Content-Type | application/json |
| Payment | x402 · USDC on Base |
| Price | $0.015 per fulfilled request |
Useful links
SDKs / Community
Veyrly uses the open x402 protocol. No Veyrly-specific official SDK is currently published; use an x402-compatible client and the OpenAPI specification.
Changelog
v0.1 — Evidence endpoint, x402 v2 payment, source validation and machine discovery.