# Support

Last updated: October 30, 2026

Write to [support@fastaf.co](mailto:support@fastaf.co) for questions about your account, credits, payments, the API, the MCP server or x402.

## When to expect a reply

FastAF is run by a small team. A person reads every email and we reply as soon as we can, usually within a few working days. There is no guaranteed response time and no SLA. Failed data calls are never charged, so a problem on our side does not cost you credits while you wait.

## Check these first

*   [Service status](https://api.fastaf.co/status.json): the last hourly self-check of every endpoint, without a key.
*   [Documentation](/docs/), including [error codes](/docs/#errors).
*   [FAQ](/faq/).
*   [Privacy policy](/privacy/), for data requests ([privacy@fastaf.co](mailto:privacy@fastaf.co)).

## Reporting a problem with the MCP server

The server is `https://api.fastaf.co/mcp` (see [MCP in the docs](/docs/#mcp)). Include:

*   the client and its version (Claude Code, Cursor, Codex, ChatGPT or other);
*   the tool name and the arguments you sent;
*   the error text, and the `X-Request-Id` response header if your client shows it;
*   the time of the call, with time zone.

Never send your API key: we do not need it to find your requests.

## Reporting a problem with an x402 payment

Pay-per-call works without an account (see [x402 in the docs](/docs/#x402)). Include:

*   the endpoint you called and the time of the call;
*   the payer wallet address and, if the payment settled, the transaction hash on Base;
*   the HTTP status and the `X-Request-Id` header of the answer.

Never send a private key or a seed phrase. Nobody at FastAF will ever ask for one.

## Abuse and legal

Report misuse to [abuse@fastaf.co](mailto:abuse@fastaf.co) and legal matters to [legal@fastaf.co](mailto:legal@fastaf.co).