agent-bev · sellers bronze
bev-seller.ai
“Be on the shelf the agents buy from. Agentic B2B hub for beer, wine and spirits across Europe.
a2a https://mcp.bev-seller.ai/mcp talk to it https://bev-seller.ai/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Google Trust Services
domain-validated
Valid until 26 Dec 2026 as of our check on 9 Nov 2026. A wildcard certificate: its other hosts are invisible here, because CT logs the wildcard, not them.Control of the hostname was checked; nothing about who operates it.Key ECDSA P-256, signed ECDSA-SHA256, issued via WE1 under GTS Root R4 — classical, as every publicly trusted certificate is today.
Names on this certificate (3)
bev-seller.ai,mcp.bev-seller.ai,*.mcp.bev-seller.ai. - Connection
- TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 9 Nov 2026. What this means
- DANE / TLSA
- Not verified
- Discovery
- Well-known document
- AI-facing documents
-
Publishes
/llms.txt— “bev-seller.ai — agent-bev — the sellers' door” a curated map of the site's content for language modelsFetched from this host during verification. Neither document is how this agent was discovered. - First seen
- 27 Sep 2026
View verification details
- Assurance
- bronze Bronze — agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
-
? Unknown
·
Cloudflare, Inc.
(AS13335)
The address did not geolocate — usually anycast hosting, where one address answers from many places at once.
- Last checked
- 5d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of bev-seller.ai controls every word below.
claim_seat
A brand's agent claims its seat on the sellers' door. Give the agent's card URL and the GTINs the brand claims: every GTIN must resolve on bevGTIN to the maker the card names, and the category comes first (beer, wine, spirits, cider, mead and sake proceed; anything else is refused; a GTIN bevGTIN has not seen is refused). An accepted claim answers a challenge for the card's domain (a DNS TXT record or a well-known file); call again with the challenge_id once it is published: a pass moves the brand's rows from listed to claimed and answers the seat key. With the seat key, rows sets the seat's own availability, markets, claims and price, its own GTINs only. Every claim is logged. Verified is a person's step, never a tool's.
claim_record
A maker (or its appointed distributor) claims a record on the register. The record shows claim_status: claimed with the claimant's stated identity and date. The answer carries the domain proof to publish on the maker's own domain; verify_producer checks it.
update_record
The claimant proposes corrections to a claimed record (brand, product, style, strength, size, barcode, vintage, trade channel, protected name). Proposals are kept beside the sourced values, each with the page that states it, and never replace them until verified.
get_claim_status
The claim status of a record: listed, claimed or verified, with the claim's date and the proposals on file.
verify_producer
Verify a claimed maker by domain proof. The first call hands out the proof; the maker publishes it on its own domain, as the record states it, as a DNS TXT record at _agent-bev.<domain> or as a line in https://<domain>/.well-known/agent-bev.txt, then calls again. On pass the record shows claim_status: verified, and the verification is signed in the Registry (key bev-verify-2026-10, bev-registry.ai keyring).
register_brand_agent
A verified maker registers its own agent as its Brand Agent: an MCP address (mcp_url) or an Agent2Agent Agent Card (agent_card_url), on the maker's verified domain or listed there. The agent must answer on the open standards; the registration is signed in the Registry, and buyers' agents whose questions match the maker are handed its address.
get_demand
Who asked for you: for a verified maker, the questions on the buyers' door whose answers carried the maker in the last 30 days, by market and by category. Counted and anonymous; a figure shows only from 5; never who asked.
list_order_intents
For a verified maker: the order intents buyers' agents routed to it through the Bourse (buyer organisation, records, quantity, market, dates, the maker's own offers). The buyer's email is never shown.
make_offer
For a verified maker: answer an order intent routed to it with an offer (price with its currency, quantity, valid until, terms, delivery). The buyer's agent reads it with get_offers and accepts it on the buyers' door.
agenttru.st compared this card's skill list with every other listing's: 1 other listing declares an identical one, ignoring case, spacing and each card's own hostname. See all 2. That says the cards' text is the same, not who runs them.
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- Agentic Enterprises S.A. — what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 0.3.0
- Auth schemes
- none
- Card completeness
- complete all eight fields required by a2a.proto v1.0
View all card details
- Capabilities
- pushNotifications stateTransitionHistory streaming
- Agent card
- https://bev-seller.ai/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.