Quick setup
Open the kRouter dashboard at http://localhost:20128
Go to Providers → click Google PSE
Paste your API key, click Save
Test the connection
Use in your IDE
Point any OpenAI-compatible client at kRouter using your local API key.
# Endpoint
http://localhost:20128/v1
# API key (from Dashboard → API Keys)
sk-krouter-XXXX
# Model
gpse/<model-id>How Google PSE billing works with kRouter
Google PSE 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, Google PSE 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 Google PSE is a one-line model change in your client rather than a rewrite.
Google PSE links
Google PSE FAQ
Is Google PSE free through kRouter?
Google PSE is pay-per-token: you bring your own API key and are billed by Google PSE at their rates. kRouter adds nothing on top and is free and MIT-licensed.
How do I use Google PSE with Claude Code or Cursor?
Connect Google PSE 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 gpse/<model>.
What happens when Google PSE 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.