Search API provider routing for AI agents.
AOPX is an evidence-based provider routing layer for software agents. It recommends a primary search provider and fallback path, then records reported production outcomes when callers send them back. The current production category is SEARCH with Brave Search and Tavily Search. AOPX does not execute the search itself.
what AOPX does
Why not call a provider directly?
You can. AOPX is useful when an agent should avoid hard-coding a single provider, needs a fallback path, or wants provider decisions to accumulate reported production evidence over time.
What AOPX is not
Not a search engine. Not a model. Not a payment processor. Not a reseller of provider results. In the current consultation model, the calling agent executes the provider itself.
current production scope
quick start
Three steps. Measurable evidence, explicit hand-off.
| # | step | who | what happens |
|---|---|---|---|
| 1 | recommend | agent → AOPX | Send category, mode and optional constraints. AOPX returns a primary provider, fallback provider and recommendation_id. |
| 2 | execute | agent → provider | The agent calls the recommended provider itself. If required, it follows the returned fallback path. |
| 3 | report | agent → AOPX | The agent may report the real production result. AOPX records it as reported production evidence for future policy evaluation. |
minimal request
POST https://api.aopx.fr/v1/recommend Content-Type: application/json { "category": "SEARCH", "mode": "CRITICAL" }
response shape
{
"recommendation_id": "REC-…",
"source": "PRODUCTION",
"category": "SEARCH",
"mode": "CRITICAL",
"status": "OK",
"provider_id": "brave-search",
"fallback_provider_id": "tavily-search",
"policy_version": "search-consult-v0.2",
"evidence_run_id": "LAB0035-E33AC6B7B4",
"reason": "engine:EXPLORATION",
"experimental": false
}
Provider order in this example is illustrative of an actual response shape, not a claim that Brave is universally preferred.
integrations
AOPX is designed to be callable by agents and workflow systems, not only by humans browsing this site.
| surface | status | entry point | use |
|---|---|---|---|
| REST API | LIVE | https://api.aopx.fr | Direct application integration |
| MCP | LIVE | fr.aopx/aopx | MCP-compatible agent clients |
| MCP Registry | LISTED | registry.modelcontextprotocol.io | Discovery |
| Glama | LISTED | glama.ai | Connector discovery / metadata |
| n8n | BETA | n8n-nodes-aopx | Workflow integration |
| Claude | PREPARATION | Remote MCP / connector route under review | Agent distribution |
api
Base URL: https://api.aopx.fr
modes
| mode | status | current behavior |
|---|---|---|
| ECONOMY | reference | Fixed provider reference path. No routing advantage claimed. |
| CRITICAL | enabled | Evidence-informed primary-provider selection plus second-provider fallback. |
| BALANCED | disabled | Initial signal did not confirm on holdout. Not available in v0. |
mcp server
Remote MCP server. Four public tools are exposed. The server is intended for MCP-compatible clients and software agents that need provider-selection or public evidence data.
| field | value |
|---|---|
| endpoint | https://api.aopx.fr/mcp/ |
| transport | streamable-http |
| registry | fr.aopx/aopx |
| tools | recommend_provider · report_outcome · public_stats · public_outcomes |
| auth | authless during pilot |
tool intent
| tool | use when | returns / records |
|---|---|---|
| recommend_provider | An agent needs a supported search provider instead of hard-coding one. | Primary provider, fallback provider, recommendation_id and policy metadata. |
| report_outcome | The caller has executed a prior AOPX recommendation. | A reported production outcome tied to the recommendation_id. |
| public_stats | A client needs aggregate public pilot telemetry. | Production-only aggregate statistics. |
| public_outcomes | A client needs the latest anonymised reported outcomes. | Recent production outcomes using public provider aliases. |
Security annotations are intentionally not claimed on this page until the deployed MCP metadata is verified against the current connector requirements.
n8n node
Community node for using AOPX inside n8n workflows.
| field | value |
|---|---|
| package | n8n-nodes-aopx |
| status | beta |
| operations | Recommend Provider · Report Outcome · Get Public Stats |
| distribution | npm package |
production evidence
AOPX separates reported production outcomes from LAB benchmarks, tests, shadow runs and replays. Public provider identities are anonymised as Provider A / Provider B in production evidence.
Public outcomes
Recent reported production outcomes exposed through the public API.
Public stats
Aggregate consultation, outcome-return and reported provider-spend telemetry.
Public evidence ledger: api.aopx.fr/lab003/evidence →
evidence vocabulary
benchmark
Public benchmark evidence is separated from production outcomes. The current headline result is LAB-003.5.
LAB-003.5 - SEARCH / CRITICAL
| path | successes | rate | interpretation |
|---|---|---|---|
| AOPX CRITICAL policy | 40 / 50 | 80% | Measured policy result. |
| Tavily fixed | 37 / 50 | 74% | Fixed-provider reference. |
| Brave → Tavily cascade | 40 / 50 | 80% | Post-hoc cascade reached the same final success rate. |
frozen artifacts
current limitations
- SEARCH is the only production category described on this page.
- Brave Search and Tavily Search are the current production providers.
- AOPX is consultation-only and does not execute search requests on behalf of callers.
- Reported production outcomes depend on callers returning feedback.
- Production history is still limited during the public pilot.
- No universal provider superiority is claimed.
- LAB-003.5 does not isolate contextual selection as the sole cause of the measured CRITICAL result.
- Billing is disabled during the current pilot.
developer faq
What is AOPX?
AOPX is an evidence-based provider routing layer for software agents. It recommends a supported search provider and fallback path and records reported production outcomes when callers send them back.
Is AOPX a search engine?
No. AOPX does not execute the search in the current consultation model. The calling agent executes the provider externally.
Which search providers are supported?
Brave Search and Tavily Search are the current production providers for SEARCH. Serper is under evaluation and is not presented here as production-ready.
Is Brave better than Tavily?
AOPX does not claim that either provider is universally superior. Its benchmark evidence shows that results vary by protocol and path, and that fallback can materially affect final success.
Why use AOPX instead of calling Brave or Tavily directly?
You can call either provider directly. AOPX adds provider selection, a fallback path, production outcome tracking and an evidence history above the individual provider APIs.
What is a reported production outcome?
It is a result returned to AOPX after a caller executes a recommendation. It is reported by the caller and is kept separate from benchmark, test, replay and shadow-run data.
