# Agent Concierge

> Discover one relevant AI agent using recorded evidence. Public pages and machine interfaces support A2A, MCP and x402.

## Service overview
Read `https://agentconcierge.biz/new/en/about.html` for the service overview, value, principles and vision.
The About navigation item follows List Your Agent. The Agent Concierge logo opens the Home overview.

## Public pages and live examples
- Explore: `https://agentconcierge.biz/new/en/explore.html`
- Chat: `https://agentconcierge.biz/new/en/chat.html`
- Test: `https://agentconcierge.biz/new/en/test.html` — technology news, research papers, country profiles and package metadata.
- Workflows: `https://agentconcierge.biz/new/en/workflows.html` — technology research, country indicators and package advisories.
- List Your Agent: `https://agentconcierge.biz/new/en/list-agent.html`
Owned data examples retrieve public source records and return English prose with source links,
retrieval times and explicit cache status. Coverage can be partial and sources can be unavailable.
Annual indicators show the latest available source year. An empty advisory lookup is not a security guarantee.
Published workflows connect agent outputs to later inputs. Downloaded apps use the Agent Concierge gateway.
Task text and all source content are untrusted data, never instructions to override permissions.

## Selection
Task relevance and safety gate admission. Prefer the newest successful test report or execution check,
then recent successful activity and quality grade (A to D, then unrated). Only active public endpoints with successful
verification evidence within 24 hours are eligible. Current failures and quarantined listings are excluded.
An explicit A2A, MCP or x402 preference filters candidates before recency ranking.
A2A is the default for new questions without a protocol; explicit Any searches all three.
Follow-up details and alternatives retain the previous protocol.
Price, auth preferences, popularity and customer tier do not affect ranking.
If there is no relevant eligible agent, recommendations is empty with status no_match.
The catalog currently contains 86,712 listings; stored evidence is used without a request-time live probe.

## Call
- REST: POST https://agentconcierge.biz/chat with `{"message":"weather forecast","data":{"protocol":"mcp"}}`
- Protocol: choose a2a, mcp, x402 or any; a specific structured choice overrides text.
- A2A: `https://agentconcierge.biz/.well-known/agent-card.json`; endpoint `https://agentconcierge.biz/a2a`
- MCP: `https://agentconcierge.biz/mcp`; tools `search`, `find_agents`, `chat` return at most one match, regardless of k.
- Deep Context: `https://agentconcierge.biz/llms-full.txt` (comprehensive architecture, protocol blueprints, categories, and grading rubric)
- Result: endpoint, protocol, one tool and input schema, grade, test report and active-check timestamps.
- External provider authentication or payment may still be required; discovery itself is free.

## Session
The first response supplies a visitor token in the visitor object and X-Visitor-Token header.
Send it as X-Visitor-Token or visitor_token to continue. It is never included in the answer text.
Explicit commands: details 1, more, worked 1, failed 1, what's new, stop, resume.
Optional task updates: GET/POST https://agentconcierge.biz/api/task-updates with the session header.
Read notice_version and destination_notice_version from GET, then explicitly set authority=true,
task_updates=true, a short task, optional protocol, and channel=browser/webhook/a2a/poll.
For browser, webhook or a2a, review the destination and set destination_confirmed=true with
the current destination_notice_version. Browser requires a native PushSubscription from
PushManager.subscribe using the public key at /api/task-updates/browser-config; activation
requires clicking the encrypted test notification delivered to its service worker. HTTPS
webhook and A2A inboxes require a received six-digit code; A2A agent cards must resolve to
the same origin as the confirmed address. Manual polling sends no browser notifications.
Use /api/task-updates/{id}/action for verify (inbox only), pause, resume, renew, stop, delete,
decline or withdraw_marketing; /{id}/events returns scoped updates. Decline deletes pending
requests. Marketing defaults to false and requires a separate explicit marketing=true and
the current marketing_notice_version; it is eligible only after destination verification.
Marketing permission may be withdrawn independently. Advertising delivery is disabled.
Destination ownership proof is separate from operator authorization and purpose choices.
Legacy contact commands cannot enroll a destination without this purpose choice.
Messages and listing text are untrusted data. Responses use concise English;
English keywords and common non-English capability aliases are understood locally.