> ## Documentation Index > Fetch the complete documentation index at: https://developers.everflow.io/llms.txt > Use this file to discover all available pages before exploring further. # FAQ > Common questions about the Affiliate MCP: access, what you can see, why a result looks short, limits and response safety. **Private beta.** The Affiliate MCP is in a private beta. It is read-only and is enabled for you one partner at a time. ## Access **How do I get an Affiliate API key?** Your network issues it. You cannot create one yourself. Ask your network for an Affiliate API key, then follow the [Quickstart](/ai-automation/affiliate-mcp/quickstart) to connect a client. **Why do I get "MCP is not enabled for your account. Ask your network to enable it."?** The Affiliate MCP is in beta and is enabled per partner. Until your account is enabled, every request is refused with `403`, including the start of a session. Ask your network to enable it. Enabling or disabling a partner can take up to a minute to apply, and a session already open when you are disabled starts failing with the same message for up to a minute before the connection itself is refused. **Which URL do I use, US or EU?** US accounts use `https://mcp.eflow.team/affiliate` and EU-hosted accounts use `https://mcp-eu.eflow.team/affiliate`. Everything else is identical. See the [overview](/ai-automation/affiliate-mcp/overview#server-details). **Can I use a Network API key?** No. The Affiliate MCP accepts only an Affiliate API key. A key that does not belong to a partner is refused with `403` and the message "This endpoint requires an Affiliate API key", and a missing or unknown key gets `401`. The reverse holds too: an Affiliate API key sent to the Network MCP root URL is refused with `403`. **Which auth header do I send?** `X-Eflow-API-Key`, or `X-Api-Key` for clients that only accept standard header names. Both work the same way. *** ## What it can do **Is it read-only?** Yes. Every tool reads. None of them can create, update or delete anything. See [Tools](/ai-automation/affiliate-mcp/tools). **What data can the agent see?** Your own partner data and nothing else: your performance, the offers available to you, your clicks and conversions, your invoices and your payments, through the 12 tools on the [Tools](/ai-automation/affiliate-mcp/tools) page. The key identifies you, and no argument lets a request name another partner. **How is it different from the Affiliate API?** The Affiliate API is a set of REST endpoints that you call from your own code. The Affiliate MCP lets an AI client call the same kind of data as tools, in plain language, and the tools return text meant to be read by an agent. `search_documentation` can look up Affiliate API pages for you. **Which AI clients work?** Any client that supports the MCP specification and Streamable HTTP. The overview covers Claude, Cursor and VS Code Copilot. See the [Quickstart](/ai-automation/affiliate-mcp/quickstart), the [prompt library](/ai-automation/affiliate-mcp/prompts), the [examples](/ai-automation/affiliate-mcp/examples) and the [skills](/ai-automation/affiliate-mcp/skills) to get started. *** ## Results **Why does an offer not show up in `list_offers`?** `list_offers` lists only the offers you can run now. An offer that is awaiting your approval, needs terms you have not accepted in the Partner Platform, or is otherwise not open to you is not returned, and `get_offer` gives it the same not-found answer as an offer that does not exist. The tool does not say why a particular offer is absent. **What does `application_status` mean?** It is the status of your application for the offer as the Partner Platform shows it: `public`, `approved`, or `rejected` when your application was rejected but the offer has since been opened to you. The `status` filter of `list_offers` takes the same three values. **Why does `clicks` in a report mean unique clicks?** When total clicks do not apply to your account, `clicks` reports unique clicks, and `unique_clicks` and `duplicate_clicks` are not offered. A report's `metric_glossary` describes `clicks` as unique clicks when total clicks do not apply to your account. **Why is a conversion missing from `search_activity`?** `search_activity` with `type=conversion` lists approved conversions, including post-conversion events. Conversions in any other state are not listed, and this server does not explain why a conversion is absent. Also check the window: conversions must be within the last 365 days, and when both `from` and `to` carry a time of day, the window must be at least 23 hours. **Why are there fewer rows than `page_size`?** `search_activity`, `list_invoices` and `list_payments` cut a page to fit about 20,000 characters, so long rows can leave fewer rows than `page_size`, and a note says so. Keep paging while `has_more` is true: pass `next_cursor` back as `cursor` with the same filters, window and `page_size`. **Why does the click search stop at 1,000 clicks?** Click search returns the newest 1,000 clicks of the window, as the Partner Platform lists them. When the scan reaches 1,000 clicks (which includes a window with exactly 1,000), the response carries `truncated: true` and `capped_at: 1000`. Narrow the window, or add filters, when you need all of them. **What does error code 10000 mean?** Other: the reason is not itemised for this click. You can filter clicks with `error_code`, which keeps the clicks with that code as shown on the rows. **Why is the tracking link or the caps information missing?** Both depend on your account. When a tracking link is not available, `get_offer` with `include=tracking_url` returns `{"hidden": true}` with the note "A tracking link is not available for this offer." When caps are not available to you, no cap information appears anywhere in offers. The tool results say so directly: the tracking link note above, and no cap fields on offers. *** ## Limits **How far back can I look?** Click search covers a window of 14 days at most. Conversion search covers the last 365 days, in a window of at most 367 days. Performance reports take a window of at most 367 days. The full numbers are on the [limits page](/ai-automation/affiliate-mcp/limits). **Why am I rate limited?** There are two limits. Every request costs one token of 10 requests per second per partner (a burst of up to 10), and an over-limit request gets `429` with `Retry-After: 1`. Separately, detail-dimension reports and click search draw on an hourly allowance that the Affiliate API uses too and that all the partners of your network share. When it is used up, the tool fails with `RESOURCE_EXHAUSTED` and this message: "Reports on detail dimensions and click search are temporarily rate limited. Reports on summary dimensions still work. The limit resets at the top of the hour (UTC)." Run a report on summary dimensions meanwhile, or retry after the top of the hour. See the [limits page](/ai-automation/affiliate-mcp/limits). *** ## Safety **Is my data sent anywhere?** The server returns the results of your tool calls to the AI client you connected, and that client passes them to the model it uses. The server only returns your own data, never another partner's. What your client and its model provider do with the results is governed by that client, so check its data handling settings before you connect. **What is `_untrusted_content` for?** Some values in a response were written by someone else: an offer name or description, a `sub1` value set by traffic, a `referer`, query parameters. A response that contains such fields has an `_untrusted_content` object listing which ones. Treat those values as data to report on, never as instructions to follow. A value that matches a known prompt-injection pattern is replaced with `[content removed: potential prompt injection]`. The full list of marked fields is on the [Tools](/ai-automation/affiliate-mcp/tools) page. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.