Windy Search for developers

Today's web is hostile to bots. Windy Search makes it agent-native — every call is authenticated with your agent's Eternitas passport, so the agent arrives with a provable identity.

passport-authenticated · EII-tier rate limits · reported to Eternitas (best effort)

👋Not a developer?

This page is the technical detail. For what Windy Search does for you and your AI, start on the home page.

🎯

POST /v1/search

The canonical agent-facing endpoint — fan-out across configured bridges, dedup, ranked results

🦁

Brave Search

Primary bridge — privacy-respecting, ~$0.005/query

🌍

Google CSE

Last-resort fallback — adapter built and wired, awaiting its production key

🔗

POST /web/fetch

SSRF-hardened URL retrieval, returned as clean visible text (scripts and styles removed)

📄

POST /web/extract

LLM-driven extraction of a page into the JSON Schema you supply

🛡️

EII-tier limits

Requests per minute set by your agent's Eternitas Integrity Index

📊

Per-passport cost cap

Monthly USD spend ceiling per passport, scaled by tier, enforced server-side

The whole surface is documented in OpenAPI — Swagger UI at api.windysearch.com/docs, machine-readable at /openapi.json. The v1 HTTP wire protocol is locked in the service repo at spec/agent-search-protocol.md.

🔑How access works

Windy Search is passport-authenticated. Every gated endpoint expects an Eternitas Passport Token (EPT) — an ES256 JWT — in the request header:

Authorization: Bearer <your-EPT-JWT>

The service verifies that signature against the Eternitas JWKS, reads the passport's Integrity Index to pick your rate-limit tier and monthly spend cap, and reports the call back to Eternitas as an integrity event.

Passports are issued by Eternitas at hatch. An agent hatched inside the Windy ecosystem already carries one — there is nothing extra to request.
There is no public self-serve signup yet. This is a developer preview for agents inside the Windy ecosystem. There is no waitlist and no sign-up form to fill in; when a public path exists, it will be documented here.
What you can see without a passport: GET /health is open, and the Swagger page lists the full surface. A gated route called without a token answers 401 — that is the gate working, not an outage.
Your first call with a passport: GET /whoami echoes back your verified claims and tier. It is the quickest confirmation that your token is good before you spend anything.

🧩Part of the Windy ecosystem

Windy Fly is the biggest consumer of this service: a Fly agent's web access routes through Windy Search — POST /web/search and POST /web/fetch — instead of scraping sites directly. Windy Chat's agent roster calls the same toolkit for its agents' web work.

Eternitas is the other half of the story: it issues the passports, keeps the Integrity Index that decides how fast an agent may call, and receives the integrity events Windy Search reports for each call (best effort — a failed report never blocks the call). Windy Search is a primary event source feeding that score.

Hooks into further Windy products exist in the codebase but are not switched on in production, so nothing else is claimed here as live.

● Phase 1 — Live

FastAPI Service

api.windysearch.com — web-access toolkit for Windy ecosystem agents, no UI

Phase 2 — Next

Chrome Extension

Eternitas identity layer for any Chromium browser — humans on the browser they already use

Phase 3 — Future

Agent Browser Fork

Standalone agentic-first browser — conditional on Phase 2 traction, not taken on speculatively

Solves the problem nobody else has: today's web is structured to BLOCK bots (Cloudflare detection, CAPTCHAs, anti-scraping). Windy Search answers with identity rather than evasion — every call is authenticated with the agent's Eternitas passport, so the agent arrives with provable identity and reputation instead of pretending to be a person. There is no app to open: it is an API your agent calls, and when a page needs JavaScript it renders that page in a real browser on the agent's behalf.