Sell web search from your New API gateway
The Search1API plugin is listed in the New API community plugin marketplace. Install it from the admin panel, add a channel with your Search1API key, and your users call web search, news, page reading, maps and more with their gateway tokens, billed at the prices you set.
What the plugin adds
Search1API on your gateway
Clients call `/search`, `/news`, `/crawl`, `/ask`, `/maps`, `/sitemap`, `/trending`, `/extract` and `/deepcrawl` on the gateway with Search1API’s own request bodies. Every path is also served under `/search1api`.
One model per endpoint
From `search1api-search` to `search1api-deepcrawl`, each endpoint is its own model, so you can price, group and grant them separately.
Billed by real usage
Each model has one usage field, `credits`. The gateway reserves the most a request can cost, then settles to the credits Search1API actually charged, so failed requests and unread pages cost your users nothing.
Install, price and call
Sign in to New API as the Root administrator. You also need a Search1API API key from app.s1.dev; new accounts include 100 free credits.
Install the plugin and add a channel — text
Set a price per credit for each model — text
Call it with a gateway token — bash
Worth knowing
If your gateway has no Community marketplace source, add https://www.newapi.ai/api/v1/community/index.json as a source.
The official Search1API SDKs and `search1api-mcp` work through the gateway: set their base URL to `{gateway}/search1api` and use a gateway token as the key.
A request uses the same credits as on Search1API directly: 1 per search or news query plus 1 per page read, 1 per crawled URL, 5 for ask, 3 per maps page, 10 for extract and 20 per deep crawl.
An upstream New API gateway with the same plugin also works, through a New API (60) channel. The charge is not reported back through it, so requests settle at the reserved amount.
What gateway operators do with it
Offer web search next to the chat models users already buy from you, on the same tokens and balance.
Give an agent platform built on your gateway a search and page reading backend without separate keys per user.
Price search higher or lower than reading pages, per model and per user group.
FAQ
Do my users need their own Search1API account?
No. The channel holds your Search1API key and the gateway forwards their requests with it. Your users only use gateway tokens and never see the key.
Does it add web search to chat completions?
No. The plugin serves Search1API’s own endpoints on the gateway. Applications call them directly, the same way they would call Search1API.
How do I set prices?
Give each model a billing expression on the `credits` field, for example `tier("credits", u("credits") * 0.004)` for 0.004 USD per credit. The price is yours to choose.
Where is the plugin’s source code?
On GitHub at fatwang2/newapi-search1api. The marketplace installs the tagged releases from that repository.