# Authentication, payment, and access

The public website, public documentation, free browser diagnostics, A2A
metadata, and public read-only MCP tools require no account or credential.

## Public requests

Never place a password, API key, bearer token, private key, cookie, recovery
phrase, regulated record, or unrelated customer data in:

- the public fit-review form;
- an MCP tool argument;
- an A2A request;
- a URL or query string; or
- a marketplace scope description.

Use redacted status codes, timestamps, stable execution or request IDs, field
names, types, and parameter paths instead of secret values.

## Paid machine purchase

The published x402 routes use marketplace-managed Base USDC settlement. A
successful direct-rescue purchase returns a private case URL and access key.
Treat both as confidential bearer credentials: store them securely, do not put
them in public logs or links, and do not share them outside the authorized
buyer team.

The public MCP server is read-only and never initiates payment. A buyer or
authorized buyer agent must intentionally approve and execute a paid route.

## Case and production access

Production access is not requested through public discovery surfaces. After a
case is accepted, provide only the smallest agreed temporary access needed for
the bounded scope. Prefer reversible, least-privilege access and remove it
after the verified handoff.

The 12-hour delivery clock does not begin until payment has cleared, the scope
is accepted, the failure is reproducible, and agreed access is in place. It
pauses when required customer-controlled access or approval is unavailable.

See the [privacy notice](/privacy), [service terms](/terms), and
[agent safety guide](/agents.md).