# Payment smoke

Payment smoke

Status: SMOKE
Price: $0.001 USDC
`GET /v1/tools/ping`
HTML: https://magentlab.com/docs/tools/ping
Markdown: https://magentlab.com/docs/tools/ping.md

Not a medical device. Not a diagnosis or dosing recommendation.

## What it computes

Confirms the x402 gate and PAYMENT-RESPONSE. Returns {ok: true, service: magent} after settle.

## When to use

Payment plumbing check. Not a product clinical tool.

## When not to use

- Not a product tool.
- Not listed on Bazaar.
- Takes no clinical input.

## Formula

```
n/a — payment smoke; returns {ok: true, service: magent}
```

## Citation

magent payment smoke
magent
magent
DOI: none

## Worked example

### Settled ping

Given: ``

1. Settle the x402 quote.
2. Response is ok=true, service=magent.


## Also searched as

- x402 ping
- payment smoke
- paywall test

## Parameters

- `probe` (string, optional): Ignored. Payment smoke test takes no input.

## Bulk (POST)

No same-path bulk POST on this path.

## Response fields

- `ok` (boolean): Always true after a successful settle
- `service` (string): Product name

## Example JSON

Frozen fixture. Not a live lookup.

```json
{
  "ok": true,
  "service": "magent"
}
```

## Errors



Shared HTTP 402 and 503: https://magentlab.com/docs/payments

## Related tools

- None

## Payment

Unpaid requests return HTTP 402 even if query parameters or POST items are missing or invalid, so CDP and agents can index the path. After a PAYMENT-SIGNATURE, invalid params return HTTP 400 JSON before settlement. Magent does not charge. Fix the params, then request a new 402 quote for that complete URL. Catalog misses (empty matches, found=false) are valid paid 200s.

- GET the tool with Accept: application/json (do not send Accept: text/html unless you want the human paywall).
- HTTP 402 means you have not paid. Decode the base64 PAYMENT-REQUIRED header. HTTP 503 is not a new quote.
- Sign accepts[0] (exact, EIP-3009) with validBefore = now + maxTimeoutSeconds (600 seconds), or accepts[1] (batch-settlement deposit/voucher) on product GET. Ping and POST {items} stay exact. Magent retries transient facilitator 429/5xx before answering.
- Retry the same URL with PAYMENT-SIGNATURE (base64 JSON of accepted and payload). Magent attaches canonical extensions.bazaar on CDP verify/settle; echoing 402 bazaar is optional.
- Success is HTTP 200 JSON plus PAYMENT-RESPONSE. exact settles before the tool. batch-settlement verifies (and deposit-settles) before the tool and commits the charge after HTTP 2xx. HTTP 503: retry the same PAYMENT-SIGNATURE. Mint a new exact nonce only after a new HTTP 402.

- offered `exact` on eip155:8453: Fixed-price USDC on Base. The buyer authorizes the advertised amount (EIP-3009). magent settles before the tool runs (paymentFlow upfront). extra.assetTransferMethod=eip3009 extra.paymentFlow=upfront.
- offered `batch-settlement` on eip155:8453: Payment-channel vouchers claimed later in batches. Exact stays accepts[0]. Same-path POST {items} is still exact. extra.assetTransferMethod=eip3009 extra.paymentFlow=authorization.

- not offered `upto`: Not offered. Usage-based: buyer authorizes a ceiling, seller settles the actual amount after work. Reserved for a future metered tool. Not for current calculators or code search.

Same-path POST {items} is still scheme exact: one EIP-3009 authorization for GET unit plus $0.002 per extra item. That is not x402 batch-settlement (payment channels / vouchers).

Shared HTTP 402 and 503 table: https://magentlab.com/docs/payments

## Guarantees

- HTTP 402 is unpaid, including a missing query. After PAYMENT-SIGNATURE, invalid parameters return HTTP 400 before settlement. You are not charged. HTTP 402 never includes the tool JSON.
- exact: settlement finishes before the tool (paymentFlow upfront). batch-settlement: verify/deposit before the tool; chargedCumulativeAmount commits after HTTP 2xx. Uncertain or failed settlement fails closed (HTTP 503). Retry the same PAYMENT-SIGNATURE.
- HTTP 402 is unpaid only. Do not sign a second authorization because of a 503.
- Execution is timeout-bounded and concurrency-capped.
- Calculator inputs are stored encrypted for allowlisted operators (Magent Console). They are not in public logs, SSH lookups, catalog, or rollups. Request logs store path without query.
