Sharvora Intelligence

Endpoints (19 live)

• GET /api/v1/service-proof — Use as a low-cost end-to-end x402 canary before higher-value calls. A successful paid response proves Sharvora delivery and returns release, network, time and a response receipt. (0.001 USDC on Base)
• POST /api/v1/web/security-headers — Use for a no-login audit of a public HTTP(S) page's major browser security headers and a prioritized list of missing protections. (0.02 USDC on Base)
• POST /api/v1/x402/validate — Use to inspect a public x402 URL without spending funds: confirms HTTP 402 behavior and decodes v2 payment metadata when available. (0.005 USDC on Base)
• POST /api/v1/web/http-policy — Use to inspect a public HTTP response's cache, CORS, cookie and browser-policy posture as a point-in-time evidence snapshot. (0.03 USDC on Base)
• POST /api/v1/web/agent-readiness — Use to audit whether a public website exposes machine-readable agent surfaces such as robots, sitemap, llms.txt/llms-full, OpenAPI, RFC 9727 API catalog, A2A discovery, x402 and security.txt. (0.02 USDC on Base)
• POST /api/v1/web/trust-passport — Use when an agent wants one integrated trust purchase: combines agent readiness, bounded endpoint-risk heuristics, redirect evidence, HTTP policy, browser security headers and TLS posture into a scored evidence passport. (0.15 USDC on Base)
• POST /api/v1/web/redirect-audit — Use to inspect a public URL redirect chain, cross-origin hops, loops and HTTPS-to-HTTP downgrade evidence with private-network redirect protection. (0.02 USDC on Base)
• POST /api/v1/web/endpoint-trust — Use before an agent trusts a public endpoint: combines bounded public fetching, redirect and browser-policy evidence, and a deterministic static scan for common prompt-injection and credential-exfiltration language. (0.05 USDC on Base)
• POST /api/v1/quant/risk-state — Use when an agent has an ordered numeric series and needs volatility, drawdown, anomaly and regime context before making a downstream decision. (0.02 USDC on Base)
• POST /api/v1/web/tls-report — Use to check a public hostname's TLS certificate issuer, SAN coverage, cipher and expiry window without requiring credentials to the target site. (0.02 USDC on Base)
• POST /api/v1/quant/flow-monitor — Use to normalize supplied exchange, bridge and stablecoin inflow/outflow values into net-flow direction and intensity context. (0.03 USDC on Base)
• POST /api/v1/quant/anomaly — Use to rank unusual observations in a supplied numeric series with transparent z-score and median-absolute-deviation evidence. (0.03 USDC on Base)
• POST /api/v1/decision/preflight — Use immediately before an automated decision to check observation age, missing context and optional series risk for explicit warning conditions. (0.05 USDC on Base)
• POST /api/v1/evidence/consensus — Use to measure agreement, freshness and contradictions across caller-supplied numeric observations with transparent confidence and weighting evidence. (0.06 USDC on Base)
• POST /api/v1/quant/forecast-range — Use for a simple probabilistic 80% range estimate from a supplied time series when an agent needs bounded uncertainty, not a trade instruction. (0.05 USDC on Base)
• POST /api/v1/decision/bundle — Use when an agent wants one payment and one response for freshness, completeness, risk, anomaly and forecast evidence over the same supplied series. (0.12 USDC on Base)
• POST /api/v1/decision/journal — Use to create a durable auditable decision record with a stable decision_id, context hash, horizon, direction and confidence for later evaluation. (0.1 USDC on Base)
• POST /api/v1/decision/audit — Use after an outcome is known to compare it with a prior Sharvora decision record and calculate change and directional hit evidence. (0.05 USDC on Base)
• POST /api/v1/evidence/receipt — Use when an agent needs a deterministic SHA-256 content-integrity receipt for exact UTF-8 text. This is off-chain and does not claim notarization. (0.01 USDC on Base)