Search. Scrape.
Stay in control.

1. Create an account

Sign in through the app, or create an agent without a browser. Save the returned secret once; it is never shown again.

POST https://search.agnt.gg/search/v1/agents
Content-Type: application/json

{"name":"research-agent","allowPrepaid":true}

2. Fund and authorize usage

Use the returned funding link or x402. Human owners enable extra usage and set account budgets in the app. Initial agent credentials carry execution, receipts and funding scopes with a $10 monthly key cap; an explicit request spending cap is also required.

3. Search

POST /search/v1/search
Authorization: Bearer YOUR_SEARCH_KEY
Idempotency-Key: unique-request-20260918-001
Content-Type: application/json

{"query":"agent infrastructure","num":5,"sort":"relevance","maxChargeMicroUSD":15000}

Returns success, query, resultsCount, and results containing title, link, snippet and source. Default 5, maximum 10. Date sort is optional. A successful empty search is charged.

4. Scrape

POST /search/v1/scrape
Authorization: Bearer YOUR_SEARCH_KEY
Idempotency-Key: unique-request-20260918-002
Content-Type: application/json

{"url":"https://example.com","mode":"standard","maxChargeMicroUSD":4000}

Returns textContent, links and codeContent. Pages render in Chrome before cleanup. Navigation and sidebar links are removed. Login-only pages, private networks, unsupported protocols, blocked/error pages and excessive content are not supported.

Payments

Stripe Checkout funds $10, $25 or $50 prepaid credit. Credit appears only after verified payment. No monthly plan is required. Requests debit prepaid credit only when explicitly authorized. No unlimited allowance.

x402 / USDC on Base

1. POST /funding/x402 with amountCents and Idempotency-Key using a funding-scoped key.
2. Read HTTP 402 and the base64 PAYMENT-REQUIRED header.
3. Authorize exactly the stated USDC amount, destination, chain and validity in your wallet.
4. POST /funding/x402/:orderId with PAYMENT-SIGNATURE.
5. Read PAYMENT-RESPONSE and the credited receipt. If pending, poll that order; never pay a second order to recover a timeout.

Search does not hold wallet signing keys. Funding does not authorize unlimited usage.

Limits & retries

• Google search costs $0.015 per successful query (up to ten results). Standard rendered scraping costs $0.004 per successful page. One search or standard scrape can use one included operation.
• maxChargeMicroUSD: 0 means included-only. Cash also requires account authorization and available account/key budgets.
• One concurrent scrape per service worker; 30 attempted operations per account per minute.
• Standard scraping has a 30-second execution limit. Opt-in mode: "extended" allows up to 195 seconds and costs $0.04 per successful page, cash-only with maxChargeMicroUSD at least 40000. No automatic escalation; configure extended clients for at least 210 seconds.
• 10 MiB rendered document, 50 MiB network transfer, 1 MiB returned JSON. Excessive content fails, not silently truncates.
• Failed requests release reservations, but attempt, failure and runtime budgets still apply. Five failed attempts per hour or 120 seconds of failed scrape runtime per account per UTC day pauses further scraping. Scrape runtime is capped at one hour/account/day and also bounded by the funded balance and allowance. Reuse the same idempotency key for uncertain retries, never a fresh key.
• We store receipts, not response content. A retry returns the receipt and resultRetained:false, without re-executing. Save the original result on your side.

Errors

400 invalid input · 401 invalid credentials · 403 insufficient scope · 402 funding/spending limit · 409 conflicting or running request · 429 rate/capacity limit · 503 unavailable provider or execution failure. Check the stable error code and request receipt before retrying.

Keys

search:execute, scrape:execute, search:read and search:fund are independent. Keys expire and can be revoked. Email sign-in is required to create keys or change spending controls. Never put API secrets in browser pages you publish.

Signed notifications

Register up to three public HTTPS receivers in the app or POST /webhooks. Save the one-time signing secret. Verify X-AGNT-Signature as v1=HMAC-SHA256(secret, timestamp + "." + rawBody), using X-AGNT-Timestamp with a five-minute tolerance. Deduplicate X-AGNT-Event-ID. Delivery is at least once with up to three attempts; history is retained seven days. Notifications contain receipts and state, never scraped content.

Privacy & acceptable use

Search queries go to Google; target websites receive scrape requests. AGNT retains account, payment and request metadata for operation and accounting, but does not persist returned page or search content. Avoid sending secrets in queries or URLs. Use only content you are permitted to access; no authentication bypass, abusive crawling or access to private infrastructure.

New monthly plans are retired. Previously purchased allowances remain valid until their original expiry and do not renew. AGNT bundles reset each UTC month; no rollover. Extended scraping is not included. Financial records are retained for accounting; request logs exclude raw query text and page bodies. Contact support@agnt.gg for account, billing or data requests.

Google currently provides the search backend and has announced a January 1, 2027 API transition. AGNT's public contract is independent of the provider.

Client downloads

Save each response when it arrives. Use the same idempotency key for an uncertain retry; receipts do not include previously returned content.