Serphouse for AI agents

Serphouse is a high-volume SERP API built for SEO companies and data mining services to pull search rankings and Google Trends data at scale. SaaS SEO tools run on it as a backend. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Developer toolsAPI keyMCP + RESTserphouse.com
AUDIT LOG · SERPHOUSEPOLICY: acme-support
09:41:09 · claude · u_8f2write
serphouse.serp_check
Check SERP Task Status✓ approved · approved by user
EVERY SERPHOUSE CALL, ON THE RECORD
01 · USE CASES

What agents do in Serphouse.

01

Check a scheduled task's status

Poll whether a scheduled SERP task has finished before pulling its results into a report.

02

Schedule a Google Trends search

Queue a Trends search for a keyword to track interest over time across a chosen region.

03

Pull ranked domains for a keyword

Retrieve the list of ranking domains for a search term to support a competitive SEO analysis.

02 · ACTIONS

18 Serphouse actions, graded by risk.

Every Serphouse action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

0

Look things up. Allowed by default.

  • No read actions.

write

18

Create and change things. Allow, or ask the user first.

  • serphouse.serp_check
    Check SERP Task Status
  • serphouse.trends_get
    Get Trend Search Results
  • serphouse.domain_list
    Get Domain List
  • serphouse.account_info
    Get Account Information
  • serphouse.trends_check
    Check Trend Search Status
  • serphouse.language_list
    Get Language List
  • serphouse.serp_live_get
    SERP Live Search (GET)
  • serphouse.serp_schedule
    Schedule SERP Tasks
  • serphouse.trends_search
    Perform Google Trends Search
  • serphouse.serp_live_post
    Execute SERP Live POST Search
  • serphouse.location_search
    Search Locations
  • serphouse.trends_schedule
    Schedule Google Trends Search
  • serphouse.google_jobs_search
    Google Jobs Search
  • serphouse.trends_country_list
    Get Trends Country List
  • serphouse.trends_language_list
    Get Trends Language List
  • serphouse.trends_timezone_list
    Get Trends Timezone List
+ 2 MORE

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · HOW IT WORKS

Serphouse in three steps.

  1. 01Your users connect SerphouseThey add their Serphouse api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, and writes like “check SERP Task Status” can wait for the user to approve.
  3. 03Any agent can actYour agent calls Serphouse through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('serphouse', {
  read: 'allow',
  write: 'ask',        // serp_check
  destructive: 'deny',  
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Serphouse connects.

Users add their Serphouse api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Serphouse connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Serphouse from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

Serphouse and Arc0, answered.

Q01

Can I use Serphouse with Claude, ChatGPT or Cursor?

Yes. Connect Serphouse to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Serphouse actions you allow.

Q02

How do users connect Serphouse?

Users add their Serphouse api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Serphouse actions can my agent take?

18 in total: 0 read, 18 write and 0 destructive, such as “check SERP Task Status”. Your policies decide which of them each agent may call.

Q04

Can I make my agent read-only in Serphouse?

Yes. Allow read actions and deny writes in the Serphouse policy. Your agent can still look things up, and any write it attempts is blocked and logged.

Q05

Can my own backend call Serphouse too?

Yes. The same Serphouse connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Serphouse into your agent.

Your users connect Serphouse once, under your brand. Your agent gets 18 actions behind your policies, with every call on the record.

Free to build · MCP + REST · Audit log on every plan