Why now
We are A2A.
Agent-to-Agent. It means your software talks to our software and the deal gets done without a person opening a browser.
For twenty-five years the way to buy anything was the same. A person searched, clicked through pages of results, compared, called, emailed, ordered. That era is over. Now a person gives an agent a task — find me this product, cleared for this market, from a licensed supplier, at the best price, and order it — and the agent does the work. The agent doesn't read web pages. It talks to other agents.
In peptides, almost nothing answers. Products cleared in one market and banned in the next, rules that live in nine regulators' registers in six languages, and no door an agent can walk through to ask the only questions that matter: is this cleared here, who may sell it to me, what does it cost, can I order it.
A2A Peptides is that door.
The crossover.
In June 2026 the internet crossed a line it will not cross back: more than half of all requests now come from AI agents, not people. Cloudflare Radar has it at 60% agents to 40% humans this week, and the gap widens every month.
The buyers have moved.
Ramp's data on paid AI use across its customer base, 2026 to date: technology 81%, finance and insurance 74%, manufacturing 61%, retail 49%, healthcare 43% — every sector up nine to fourteen points since December. More than half of all businesses on the platform now pay for AI. Their agents are already out there, tasked, looking for a counterparty that can answer.
The category.
Peptides are a $46–52 billion global market in 2024, projected at $93–115 billion by 2032 — almost all of it prescription medicine, the fastest-growing part of it the GLP-1 class; cosmetic and bioactive peptides are $4–5 billion, growing 6–8% a year. Every dollar of it will be bought by an agent before the decade is out.
What you get
The record.
Every peptide medicine, cosmetic and supplement that is cleared to trade in 35 countries — what it is, where it's cleared, who is licensed to supply it, where it's on shelf, what it costs. One place, kept current, read by your agents. The product knowledge of a whole category, in the form a machine can use.
A registry for security.
Every answer the hub gives can be checked. Which rule it was judged against, in which country, on which date, from which regulator's page — stamped on the answer and verifiable by your compliance team, your auditor and your regulator. In a category where the wrong answer is an illegal order, that is the difference between information and evidence.
x402 to pay on it.
Agentic commerce, not just agentic search. Your agent asks, the hub answers, your agent pays and the order settles — machine to machine, with a receipt naming exactly what was bought, where and under which rule. The checkout was built for people; this is the step after it.
Who it's for
A2A Peptides is a business-to-business agentic toolset for the parties authorized to handle peptide products — pharmacies, prescribers, wholesalers, manufacturers, brand owners and their AI agents — operated by GreenCore Solutions Corp. (GSC).
If your business is licensed to buy, sell, prescribe or dispense peptide products, your agents now have one place to ask: is this cleared here, who may supply it, what does it cost, can I place the order. If it isn't, the hub tells your agent so, and points it to a licensed provider who can help.
Research-use stock is not listed and not sold.
The gate
Three calls come before any price, availability, order or handoff: resolve_jurisdiction, then resolve_actor, then gate_transaction. The gate returns allow, deny or require_rx with a frozen reason code and the version of the rule set it read. The reason code and the rule-set version travel on every downstream receipt, including x402 settlement receipts.
The gate reads one rule set per jurisdiction: US, CA, MX, EU (member as a parameter), UK, Korea, Japan, Singapore and Switzerland — nine rule sets in force, nineteen versions on the record. A federal pass is not a state or provincial pass; an overlay row can only tighten, never loosen. A rule set is versioned and dated, never edited: a change on a register produces a new version that says what it supersedes, and the old version stays readable.
Product-level information is scoped to authorized trading partners — manufacturers, repackagers, wholesale distributors, dispensers and third-party logistics providers holding the licence that qualifies them in their jurisdiction — and to prescribers. Everyone else receives status, class-level information and a referral to a licensed provider.
- Patient (business to consumer) — cosmetic and supplement pathways, plus a referral to a licensed channel. No vial checkout.
- Prescriber, pharmacy or 503B, wholesaler (business to business) — compounding eligibility, licensed supply, price.
- Agent (agent to agent) — must present a credential. No credential returns DENY_UNLICENSED_AGENT.
- Reason codes — ALLOW · REQUIRE_RX · DENY_UNLICENSED_AGENT · DENY_ACTOR_CLASS · DENY_PATHWAY_NOT_CLEARED · DENY_JURISDICTION · DENY_STATE_OVERLAY · DENY_RUO · DENY_CONTROLLED · DENY_NO_SERIALIZATION · DENY_EXPIRED_LICENCE · DENY_CROSS_BORDER.
The door
The Model Context Protocol (MCP) door of record is mcp.a2a-peptides.ai/mcp, a stateless streamable-HTTP server named a2a-peptides with twenty tools at version 1.4. The tool list does not grow with the status table; a later version adds at most six tools and no shape change. Discovery is the signed Agent Card, not a tool. Tenant is a parameter on the supply tools, not a tool.
The ontology is substance × presentation × jurisdiction × pathway × actor. Pathways: licensed medicine, lawful compounding, cosmetic, food or supplement, and the status-only class ruo_not_cleared.
Every presentation resolves on the Agentic SKU Matrix (BSFRDP) — Brand · Strength · Form · Route · Device · Pack — the same six axes in every jurisdiction. Every response that returns a presentation carries the six axes plus the disclaimer; every tool response carries a notice stamped with the jurisdiction and rule-set version it was read against.
Every item carries availability — banner, points of sale and product page where the shelf is machine-readable.
- Gate (3) — resolve_jurisdiction, resolve_actor, gate_transaction. Called first; returns allow, deny or require_rx with a reason code.
- Regulatory truth (5) — get_substance_record, get_pathway_status, get_compounding_eligibility, get_label_and_indication, get_enforcement_watch. What the registers say, with the source page on every field.
- Cleared catalogue (3) — search_cleared_items, get_item, compare_presentations. Only what passed the gate.
- Licensed supply (3) — find_licensed_supplier, get_availability, get_price. Licensed parties only; tenant is a parameter, not a tool.
- Quality (2) — get_lot_coa, verify_serialization. Lawful lots and serialisation.
- Commerce (2) — create_order_intent, a2a_handoff. An order intent after the gate; the handoff to the counterparty agent.
- Operations (2) — get_safety_label, log_audit. Safety label and the audit line.
Agents connect from the stock client paths of the three major clouds with no adapter; the setup page carries the connection details. Registry-truth tools are metered by x402; create_order_intent settles by x402; receipts are signed and carry the reason code and the rule-set version.
The record
Every field on every record is {value, source_url, read_by, state}. A value with no source page does not exist on this graph. read_by is the engine or hand that read the source, dated. state is current, superseded or withdrawn. Counts are produced from records at request time, never typed.
Three record types carry the market. A substance record is one per molecule: International Nonproprietary Name (INN), Unique Ingredient Identifier (UNII), Chemical Abstracts Service (CAS) number, International Nomenclature of Cosmetic Ingredients (INCI) name, sourced aliases, class, one pathway row per jurisdiction and pathway, dated enforcement events and safety references. A presentation record is one per authorised presentation, never per molecule: brand, strength, form, route, device and pack, its identifiers, its holder, its licence state, serialisation, lawful lots and per-tenant offers.
A provider record is one per licensed party per jurisdiction: pharmacies, compounders, prescribers, telehealth operators and wholesalers, with licence type, number, issuer, expiry and practice scope, read from licence registers — never from directories or affiliate lists. 24,694 on the record.
Status strings are frozen and dated: approved_drug · 503A_listed · 503A_recommended_pending · 503B_listed · shortage_copy_ok · compounding_provincial_ok · magistral_ok · specials_only · cosmetic_ok · novel_food_ok · nhp_licensed · supplement_ok · prohibited · ruo_not_cleared · controlled_substance. A committee recommendation is not a listing; 503A_recommended_pending and 503A_listed are different strings.
Research-use rows exist on the substance record as a status-only class so the gate can refuse with a reason code. No presentation, offer, lot or certificate of analysis is ever created for such an item, and research-use vendors are never supplier records. Research-use stock is not listed and not sold.
The registers
Registers are sources; engines are readers. A field's source is always a register page or an official document, never a reader's answer. One reader module per register: fetch, parse, field with source and read date, state. A change on the register produces a new state, never an edit.
- US — the approved-drug and biologics registers, the bulk-substance lists for compounding under sections 503A and 503B, committee dockets and votes, the shortage list, proposed and final rules, warning letters, import alerts, cosmetic registration and listing, supplement notifications, and state pharmacy-board overlays.
- CA — the drug product database (DIN), the notice-of-compliance database, licensed natural health products (NPN), cosmetic notification, provincial compounding standards, recalls and safety alerts.
- MX — the sanitary registration for medicines and devices, the official standards for food and supplement labelling, cosmetic operating notices, and health alerts.
- EU — the Union register of medicinal products and its assessment reports, national marketing-authorisation databases with the member as a parameter, the cosmetic ingredient database and product notification portal, the novel-food list and consultation register, pharmacovigilance public pages, and the falsified-medicines serialisation regime.
- UK — the licensed-products list, specials guidance, the cosmetics regime, the novel-foods register, the adverse-reaction scheme, and enforcement and seizure notices.
- Korea — the Ministry of Food and Drug Safety: the integrated drug information system, the functional-cosmetics register, the health functional food register.
- Japan — the Pharmaceuticals and Medical Devices Agency (PMDA) and the Ministry of Health, Labour and Welfare (MHLW): the approved-drug database, quasi-drug listings, the food-with-function-claims database.
- Singapore — the Health Sciences Authority: the register of therapeutic products, cosmetic notification, health supplement guidance.
- Switzerland — Swissmedic: the authorised medicinal products list; cosmetics and food supplements under the federal ordinances.
- Cross-cutting — the INN lists as the spine for the substance identifier, UNII, CAS, INCI, and the Global Trade Item Number (GTIN) where a presentation carries one.
Shelf availability comes from the dominant licensed pharmacy chains and online pharmacies in each jurisdiction; government product registers supply the licence footnote, never the shelf.
Registers behind a login, a paywall or a wall are declared as gaps and handled by a person; the door never guesses across them.
The family
- a2a-peptides.ai — the hub: brand, signed Agent Card, the MCP door at mcp.a2a-peptides.ai, docs, setup, order-intent handoff.
- peptides-registry.ai — the registry: the status table as a product, signed records, a resolver, metered truth.
- peptides-x402.ai — the payments door: settlement and the per-resolve meter.
- a2a-pharma.ai — the pharma gate: a credentialed entrance for marketing-authorisation holders onto the same door; the Platinum Port lead.
- peptides-usa.ai — the declared-virtual showcase tenant: the template every signed tenant gets on their own domain.
- 64 forwarding zones — every twin, typo and singular form, and every mcp-peptide name, forwards with a 301 to its canonical .ai and keeps no content.
A tenant is a supplier record, catalogue rows and a signed Agent Card on its own hostname. One codebase, one status table, ten to fifty tenants. Tenants never get repositories.
Rulings of record
- Brand: a2a-peptides.ai is canonical, hyphen everywhere. Unhyphenated and singular forms forward only. The Model Context Protocol (MCP) door is a subdomain of the hub, never a second hostname.
- Judged as a machine surface: names, marks and copy are read by agents, registries and tokenizers.
- Data model and door pattern come from the public-company knowledge-graph door: nodes, an entity resolved by identifier, sourced aliases, dated events, versioned rule sets per jurisdiction. Site chrome and design come from agent-kg.ai. Gate and order-close come from the GSC doors already on the wire.
- x402 is 100% of the design: settlement after the gate, and a per-resolve meter on the registry's truth tools.
- Multi-tenant from day one: one codebase, one status table, 10 to 50 tenants. A tenant is a supplier record, catalogue rows and a signed Agent Card on its own hostname.
- Peptides USA is the declared-virtual showcase tenant on peptides-usa.ai: declared on every surface, real or no Global Trade Item Numbers (GTINs), never invented, and never counted in public numbers.
- Research-use stock is a status-only class: the door names it, refuses it with a reason code, and no commerce tool touches it. It is not listed and not sold.
- Icon of record: the node on its own, a solid disc with a light-blue centre on a transparent background. Hub blue, registry navy, x402 teal.
- The fence: every peptide record that can carry a source, across all pathways and nine jurisdictions; the gate decides who sees what.
- The disclaimer of record: Artificial intelligence makes mistakes. A2A Peptides is an information source, not a recommendation. Rules differ by jurisdiction — refer to the regulator in your jurisdiction for the information that applies to you.
- UK naming: the jurisdiction is written UK in every human-readable string; the ISO code stays in the machine fields.
- USA region: all A2A Peptides compute runs in a USA region; South Central US is the default.
- The Agentic SKU Matrix (BSFRDP): Brand · Strength · Form · Route · Device · Pack, the same six axes in every jurisdiction; BSFRDP-D carries the disclaimer as the seventh slot on every resolved presentation.
- authorized_trading_partner is the parent actor class — manufacturer, repackager, wholesale distributor, dispenser, third-party logistics provider — with prescriber beside it; product-level information is scoped to those classes.
- The provider directory: one record per licensed party per jurisdiction, read from licence registers, never from directories or affiliate lists; a referral for the public, a licensed party for the trade.
- The shelf rule: shelf availability comes from the dominant licensed pharmacy chains and online pharmacies in each jurisdiction; government product registers supply the licence footnote, never the shelf.
- Korea, Japan, Singapore and Switzerland added: nine jurisdictions, nine rule sets in force, nineteen versions on the record.
- 35 countries is the public number; nine jurisdictions and nine rule sets are the machine and record wording.
- The hero of record: Surface 1.0 — the five lines of proof in their order; no 0-reading tile ever renders.
- The no-tracking banner: a statement, not a consent request; shown at the foot of the viewport, dismissible, held in memory only; the same on every zone in the family.
Machine kit
Everything on this page is served for machines at these paths, each answering 200:
- /.well-known/agent-card.json — A2A Agent Card, signed ES256 under kid a2ap-2026-09
- /.well-known/jwks.json — the hub keyring
- /llms.txt — the plain-text guide for language models
- /ai-catalog.json — the resource catalogue (also /.well-known/ai-catalog.json)
- /index.md — this page as Markdown (also by Accept: text/markdown)
- /docs — the door's reference
- /setup — the connection page
- /icon.svg — the mark, with /icon-512.png and /icon-512-dark.png
- /site.webmanifest — the web manifest
- /health.json — surface status
- /.well-known/security.txt — the security contact
- /robots.txt — crawl policy, open
- /sitemap.xml — the sitemap
- /disclaimer — the disclaimer of record
- /legal — who operates this
- /terms — terms of use
- /privacy — privacy
- /no-cookies — no cookies, no tracking
- /security — report a security issue
- /status — live status from health.json
- /support — support
Contact
A person reads the form. Tenancy, registry and supply questions arrive here.
The form is the only human door on this surface. Machine contact is on the Agent Card and in the headers.