The agentic hub for the peptide industry — Agent-to-Agent (A2A) and Model Context Protocol (MCP), on cleared rails.What this is
A2A Peptides is GSC's cleared-commerce hub for the peptide industry: a jurisdiction-and-pathway gate that only exposes items cleared to transact, with a catalogue behind it that only holds what passed.
Research-use and “research peptide” stock is a reject class the door names and refuses; zero commerce tools touch it. There is no research and development on this surface.
The hub is judged as a machine surface: its names, marks and copy are read by agents, registries and tokenizers. What a person sees here is the same record an agent reads through the door.
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) and GB. 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.
- 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.0. The tool list does not grow with the status table; version 1.1 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 reject class ruo_not_cleared.
- 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.
Two 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.
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.
The reject class exists on the substance record so the gate can refuse with a reason code. No presentation, offer, lot or certificate of analysis is ever created for a reject-class item, and research-use vendors are never supplier records.
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.
- GB — the licensed-products list, specials guidance, the cosmetics regime, the novel-foods register, the adverse-reaction scheme, and enforcement and seizure notices.
- 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.
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.
- peptides-usa.ai — the declared-virtual showcase tenant: the template every signed tenant gets on their own domain.
- 63 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 reject class. The door names it, refuses it with a reason code, and no commerce tool touches it.
- 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.
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
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.