Getting started
A few steps to get your agent on the live web.
*Typical server-side latency is a service-wide reference figure, not a measured per-account value; end-to-end varies with your network, region, and connection.
Keys authenticate your requests. Use Authorization: Bearer blp_live_…
| Name | Key | Monthly cap credits | Created | Last used | |
|---|---|---|---|---|---|
| Loading… | |||||
Keys are shown in full only once, at creation time. Store them somewhere safe — Blopus only keeps a masked preview.
Daily usage rollups, endpoint and key breakdowns, and a few cheap live counters.
At a glance
current periodRequests and credits are both real, summed from your daily rollup. Credits are the billed unit — a request asking for more results spends more than one. *Typical latency is a service-wide reference figure, not a measured per-account value.
Requests per dayiTotal API calls per day (search + fetch), from your daily rollup. Use the 7 / 30 / 90-day range toggle.
From the daily rollup · total in range: —
By endpointiShare of your calls this period by tool. Each row includes both REST and MCP calls (e.g. mcp.search counts under search, mcp.images under images), so the three add up to your total.
Share of calls this period
fetch pulls a specific URL's fresh content on demand. Image search finds pictures by what they show — every row bills the same: 1 credit per block of 10 results.
Usage by keyiPer-key usage this billing period. Requests is how many calls the key made; credits is what those calls cost, and credits are what your plan allowance and any per-key cap are measured in — one search returning up to 10 results costs 1 credit, larger result sets cost 1 per block of 10.
This billing period · from the daily rollup
| Key | Requests | Credits | Key cap | Share |
|---|---|---|---|---|
| Loading… | ||||
Alerts
We'll email your account email when usage crosses these thresholds.
Manage these in Account & Security.
Your plan, usage against the cap, top-ups, and everything about your subscription.
All plans include the same features — search & fetch tools and the hosted MCP server. Plans differ only in the monthly search cap. Every plan is hard-capped: calls pause at the cap, never a surprise bill. One search returns up to 10 results and costs 1 credit; larger result sets cost 1 credit per block of 10, up to 50 results.
Need a few more this month?
Applies to the current billing periodOne-time boost — still no overage. You only add exactly what you choose, then you are back to your plan's cap.
Manage my subscription
Change or cancel your plan, update your payment method, and download invoices and receipts. This opens the secure Stripe Customer Portal.
Blopus never receives or stores your card number. Card details are entered on Stripe's systems, and your subscription is managed there too.
Billing history
Every payment on your account. Payments are processed by Stripe — this list is read live from Stripe each time you open it, and each row opens Stripe's own receipt or invoice for the full detail.
Receipts and invoices are issued and hosted by Stripe. Blopus keeps no record of your card and does not store these transactions.
Connect the hosted Blopus MCP server, or call the REST API directly.
Quick connect
Drop this into your agent's MCP config, or hit the REST endpoint. The snippets below use one of your own keys.
{ "mcpServers": { "blopus": { "url": "https://mcp.blopus.ai", "headers": { "Authorization": "Bearer blp_live_…" } } } }
curl https://api.blopus.ai/v1/search \ -H "Authorization: Bearer blp_live_…" \ -H "Content-Type: application/json" \ -d '{ "query": "latest on small language models", "count": 5, "freshness": "pw" }'
import requests resp = requests.post( "https://api.blopus.ai/v1/search", headers={"Authorization": "Bearer blp_live_…"}, json={ "query": "latest on small language models", "count": 5, "freshness": "pw", # pd | pw | pm | all }, ) print(resp.json()["results"])
Two tools are available on every plan: search (with a freshness param — day / week / month / all) and fetch. The hosted MCP server is bundled in every plan.
Connect any agent in under a minute. One key, one endpoint — pick your tool for a copy-paste snippet and its official docs.
Plus any MCP client or tool-calling agent. If your model or framework can call a tool — natively over MCP, or as a function in any agent loop — Blopus drops right in. One key, one endpoint, no lock-in.
Reach the Blopus engineering team directly. To get a useful first reply, include
the endpoint you called, the time it failed, and your key prefix — the short
blp_live_ab12
part, never the whole key.
| Subject | Category | Status | Replies | Last activity |
|---|---|---|---|---|
| Loading… | ||||
Closed requests stay here for your records. A closed request no longer counts towards your open-request limit.
Your profile, sign-in methods, two-factor authentication and account controls.
Profile
Your name and the email you sign in with.
Password
Change the password you use for email sign-in.
Two-factor authentication (2FA)
Adds a time-based code from an authenticator app (TOTP) on top of your password.
Use an authenticator app like Google Authenticator, Authy or 1Password. 2FA is disabled by default on new accounts.
Account recovery
Set these now, while you can. They are what gets you back in if you lose your phone and your recovery codes.
Recent security activity
The last few events from your account's audit log.
| Event | IP address | When |
|---|---|---|
| Loading… | ||
Notifications
What we email your account email. Turning something off never affects billing or security email.
Danger zone
Irreversible and destructive actions.