# SpyFu setup for PopMCP You paste one value, the Base 64 Key from Account Settings, API Usage in SpyFu. It holds your API ID and Secret Key together, so there is nothing else to fill in. - Auth: API credentials - Setup time: 1 min - API base URL: https://api.spyfu.com - Credentials screen: https://www.spyfu.com/account/api - Provider docs: https://developer.spyfu.com/ ## Approval required before this works SpyFu's pricing guide says API access is included with its Pro + AI and Team/Agency plans. Nobody reviews anything: the key is already on your account's API Usage page. - Typical wait: None once the plan includes API access. The key is on the page straight away. - Cost: Prices are on SpyFu's pricing pages. On top of the plan, SpyFu bills research calls per row returned, and each tool states the price per 1,000 rows. Your plan includes a monthly API credit, and SpyFu charges anything above it to your payment method. PopMCP does not add a charge for SpyFu's API. - Blocked until approved: Without API access on the plan, SpyFu refuses the key, so nothing connects. - Works meanwhile: SpyFu's web app works on its own. Nothing in PopMCP works until the key is accepted. ## Before you begin - A SpyFu plan with API access. SpyFu's pricing guide says it is included with Pro + AI and Team/Agency. - A payment method you are happy for SpyFu to charge. SpyFu bills research calls per row returned, and anything above your plan's monthly API credit goes to that payment method. ## Get your credentials ### 1. Open API Usage in SpyFu Sign in to SpyFu, open Account Settings, then API Usage. The page lists your API ID, your Secret Key and a Base 64 Key, and shows what the API has cost this month. Screen: https://www.spyfu.com/account/api ### 2. Copy the Base 64 Key Copy the value labelled Base 64 Key. It is your API ID and Secret Key joined together, which is why it is the only thing PopMCP asks for. The Secret Key on its own is not enough. Screen: https://www.spyfu.com/account/api ### 3. Paste the key into PopMCP Paste it into SpyFu Base 64 Key. PopMCP checks it by reading your API usage for this month, which has no per-row charge. ## Fields PopMCP asks for - SpyFu Base 64 Key (apiKey) [required]: From Account Settings > API Usage in SpyFu: copy the value labelled Base 64 Key. Stored encrypted, used server-side only. ## Verify PopMCP shows SpyFu as Verified. Ask for your projects: spyfu_list_projects answers with each project's id and name, with no per-row charge. Ask about any domain to try research: spyfu_analyze_domain answers with its stats, competitors, keywords and pages, and says the most those rows could cost. ## Troubleshooting ### "Paste the Base 64 Key" Cause: The value pasted was the Secret Key or the API ID on its own, or it was copied incompletely. Fix: Copy the value labelled Base 64 Key from Account Settings, API Usage. ### "SpyFu did not accept that key" Cause: The key has been replaced, or the plan does not include API access. SpyFu gives the same answer to both. Fix: Copy the Base 64 Key again. If it still fails, check that your SpyFu plan includes the API. ### A tool asks you to confirm a large page Cause: More than 1,000 rows were requested from a tool SpyFu bills per row. The message says the most that page could cost. Fix: Tell the AI to go ahead if the cost is fine, or ask for fewer rows. ### A tool answers 429 Too Many Requests Cause: SpyFu limits each endpoint per second, and some are low. Fix: Wait a second and try again. PopMCP retries these on its own first. ### A research list comes back empty Cause: SpyFu has no rows for that site, keyword or market, or the filters ruled everything out. Fix: Remove filters, or try another country code. The default market is the US. ### A change failed with a server error Cause: SpyFu had a problem and the change may or may not have gone through. PopMCP does not repeat changes on its own, so nothing is created twice. Fix: Check the current state in My SpyFu, then try again if it is needed. --- Source: https://www.docs.popmcp.com/docs/integrations/spyfu/