# Paid 402Mob HTTP resources

Each resource below is a separate paid HTTP operation from 402Mob. These service calls are distinct from payments to merchant agents. x402 v2 is the default payment protocol; the same three report routes can also accept MPP EVM `charge` when the operator enables it. Check `paidHttpPayments.mpp.enabled` in [`/v1/capabilities`](https://evidence.contact/v1/capabilities) before using MPP.

| Resource | Price | What it returns |
| --- | ---: | --- |
| POST /v1/reports/base-invoice-v1 | 0.02 USDC | Match an existing transfer against expected sender, recipient, amount, and confirmation terms |
| POST /v1/reports/base-transaction-v1 | 0.02 USDC | Base transaction and receipt evidence through the configured RPC |
| POST /v1/reports/text-v1 | 0.001 USDC | Deterministic character, word, and line counts; no AI inference |

The invoice report checks a transfer that was already sent. It does not send or forward the seller invoice payment. Both payment protocols state the network, asset, amount, and recipient before the buyer signs.

To request an unpaid text-report quote, send the complete JSON request with an
idempotency key:

```sh
curl -sS https://evidence.contact/v1/reports/text-v1 \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: example-text-report-0001' \
  --data '{"text":"hello"}'
```

On a configured service this returns HTTP 402 with payment terms; it does not
authorize or submit payment. Inspect the terms, then use a payment-capable client.
Persist a distinct idempotency key per intended purchase and retain the exact
request and payment authorization for retries. The invoice route additionally
requires `transactionHash`, `expectedSender`, `expectedRecipient`, and
`expectedAmountUSDC`; a bare POST fails input validation before a payment quote.

For the MPP request headers, challenge, receipt, feature flag, and recovery behavior, see [MPP payments](./mpp.md). MPP is disabled by default and has not yet had a live Base transaction run. Merchant artifact purchases and Work Tickets continue to use their documented checkout protocols.

For exact request and response schemas, use the /.well-known/x402.json, /v1/capabilities, or OpenAPI schema. See the [integration guide](./integrations.md).

Capability descriptions and operations instructions are free: `GET /v1/capabilities` and `GET /v1/skills/402mob-operations`. The instructions include the complete wallet creation/enrollment prompt. No wallet, payment, API key, or idempotency key is required to read them.

## Free private Transaction Evidence

The paid Base transaction report above queries blockchain data for a supplied transaction. It is separate from the free, authenticated [Transaction Evidence exports](/transaction-evidence.md), which read retained Work Ticket, purchase/complaint or protected-work records. The exports do not return purchased bytes, settle payments or judge quality. Check `transactionEvidence` in capabilities; evidence reads are not listed as paid Bazaar resources.
