Skip to main content
kRouter
All providers

Pay-per-token

searchapi/

SearchAPI

SearchAPI — connect via API key.

www.searchapi.io

Quick setup

  1. Open the kRouter dashboard at http://localhost:20128

  2. Go to Providers → click SearchAPI

  3. Paste your API key, click Save

  4. Test the connection

Use in your IDE

Point any OpenAI-compatible client at kRouter using your local API key.

ide configbash
# Endpoint
http://localhost:20128/v1

# API key (from Dashboard → API Keys)
sk-krouter-XXXX

# Model
searchapi/<model-id>

How SearchAPI billing works with kRouter

SearchAPI is pay-per-token. You bring your own API key and kRouter routes to it, so you keep your own rate limits and billing relationship. kRouter authenticates it via apikey.

Through kRouter, SearchAPI serves web search, exposed on /v1/search so an agent can look things up mid-conversation. Requests reach it through the same local OpenAI-compatible endpoint as every other provider, so switching to or from SearchAPI is a one-line model change in your client rather than a rewrite.

SearchAPI links

SearchAPI FAQ

Is SearchAPI free through kRouter?

SearchAPI is pay-per-token: you bring your own API key and are billed by SearchAPI at their rates. kRouter adds nothing on top and is free and MIT-licensed.

How do I use SearchAPI with Claude Code or Cursor?

Connect SearchAPI in the kRouter dashboard, then point your tool at kRouter's local endpoint (http://localhost:20128/v1) with a kRouter API key. Any OpenAI-compatible client works, and models are addressed as searchapi/<model>.

What happens when SearchAPI is rate limited?

kRouter detects the limit, parks that account until its real reset time, and fails over to your next connected account or provider — so the request still completes instead of erroring.