Evidexa
Payments and refunds
Paid access is temporarily paused. Monthly fiat subscription is planned but has no checkout or entitlement; current pay-per-call requests stop before payment or Provider work. The sections below preserve the contract for earlier settled calls and any future re-enabled x402 service.
Public beta policy · effective 2026-08-20 · last updated 2026-08-22.
Before payment
The planned monthly subscription does not currently accept a card, bank authorization, checkout, or account/API-key entitlement; its plan, renewal, cancellation, refund, and billing terms will be published before activation. While pay per call is paused, a paid REST request returns HTTP 503 EVIDEXA-503-PAID_ACCESS_PAUSED with no payment requirement or charge, and a paid MCP Tool stops before Provider or x402 work. If x402 is re-enabled, a valid unpaid request receives an HTTP 402 or MCP payment requirement that identifies the Tool, amount, asset, network, recipient, and validity window. The client or Agent must validate those terms against its authority and budget before signing. Evidexa never asks for or holds a buyer private key.
When a charge occurs
A successful onchain settlement is the authoritative charge. A payment requirement, rejected preflight, invalid proof, failed verification, failed settlement, or unpaid error is not a successful charge. For an async Intelligence Job, HTTP 202 confirms authorization and reports billing.charged: false; settlement occurs only after the background Provider operation succeeds.
Delivered results
A schema-valid ok, partial, or no_data result is a delivered call because Evidexa performed the requested bounded retrieval and analysis. A valid delivered and settled call is generally final even when sources are sparse, confidence is low, or the result does not support the client's preferred conclusion.
Safe retries
After a lost or ambiguous response, reuse the same eligible client request ID or protocol payment identifier and identical input according to the documentation. A stored result may be replayed without a second proof, Provider call, or settlement. If Evidexa reports EVIDEXA-409-PAYMENT_OUTCOME_UNKNOWN, stop and contact support rather than creating a fresh payment.
Refund review
You may request manual review for a duplicate settlement, an incorrect amount or recipient generated by Evidexa, or a successful settlement where an Evidexa failure did not provide a recoverable result. Valid delivered calls, client input or wallet errors, ordinary partial or no_data results, and failures that never settled are not normally refundable. No refund is automatic, and security, technical, and compliance checks may be required.
Refund method
An approved x402 refund cannot reverse the original push payment. Evidexa issues a new USDC transfer to the original payer address on the same supported network when technically and lawfully possible. Public blockchain fees, timing, and records remain outside Evidexa's direct control.
Requesting review
Contact support@okmybot.com as soon as practical with the Evidexa request ID, Tool, approximate time, public transaction hash, and a short description. Never send a private key, seed phrase, payment signature, retry ID, raw access token, or Guest Key. This policy does not impose a deadline that shortens applicable mandatory rights.