Get your AI agents past the gate. Compliantly. At scale.
Verified-edge egress for production AI workloads - LLM training, enterprise automation (RPA, ERP, CRM), market intelligence, agentic AI products. One credential, every destination. A signed, non-repudiable access record per request - built for the regulatory environments AI operators have to work in.
A third of the internet is automated.
None of it has a verifiable identity.
Treating AI agents as scrapers is yesterday's framing. The much bigger workload is automation - agents running RPA, ERP and CRM workflows, enterprise systems calling each other, market intelligence pipelines. Extracting data is a small slice; orchestrating actions is the rest. While most of the industry races to identify agents at layer 7 - after the application sees the request - agents are blocked one layer earlier, at layer 4. At the gate, before any header is ever read.
IP addresses are already the internet's identity layer.
They just need upgrading for the agentic era.
- Geo-location
- Org ownership (WHOIS)
- Network type
- ASN reputation
- Operator accountability
- Purpose of the action (read, transact, automate)
- Access authorisation
- Commercial settlement
The industry is trying to bolt this on at L7 - header signatures, well-known endpoints, manifests. None of it helps an agent that's already been dropped at the L4 gate before any header is read. Metro Fabric closes the gap one layer down: a verified identity carried in the egress itself, settled automatically between the operators sending traffic and the destinations receiving it. Two sides of the value chain, one neutral primitive between them.
Built for AI operators.
Made viable by publishers and carriers.
Production AI agents past the gate - for the work you're already doing.
Whatever your agents are automating - ERP and CRM workflows, marketing operations, research, customer-facing AI products - Metro Fabric is the egress and identity layer that keeps them out of the block list. One credential covers every destination that integrates the registry. Every access leaves a signed, non-repudiable record - a paper trail your team can hand to legal, not a User-Agent string.
For AI operators →- Verified-edge egress that passes the L4 gate
- One credential, every destination - no per-publisher onboarding
- Signed access record per request - attribution that didn't exist before
Visibility on AI traffic, not just blocks.
Verified AI traffic carries a signed identity credential. Bot-defense savings as verified traffic skips the gauntlet. A non-repudiable record of who accessed what - attribution that didn't exist before. The integration is a one-time CDN configuration.
For publishers →The partner that anchors trust.
Not a buyer of the fabric - the rails it runs on. Under-monetised local network capacity becomes the identity layer of the agentic web. We bring the customers; you earn on standard transit services you already sell.
For telcos & ISPs →The use cases that get blocked today.
Production AI agents are already running inside enterprise. Metro Fabric is the egress and identity layer that makes them work - past the L4 gate, in any jurisdiction.
ERP & CRM agents.
The largest production AI workload inside enterprise today. Agents running procurement, finance ops, supplier portal interactions, lead enrichment, customer outreach, account research - against SAP, Oracle, Workday, Salesforce, HubSpot, Microsoft Dynamics.
Campaigns, ad ops, brand protection.
Campaign personalisation, ad verification, brand protection, counterfeit detection, programmatic content checks. Agents touching e-commerce sites, ad networks, and competitive surfaces - at volume that gets blocked at the edge.
LLM training & agentic products.
LLM training, web-scale research, knowledge-graph construction, real-time answer-engine retrieval, customer-facing agentic products that need reliable web access on behalf of their users.
The agent reaches the destination.
Compliantly. With less risk.
Past the L4 gate.
Your agent gets past the L4 gate. No more datacenter blocks, rotating shadow IPs, or per-publisher workarounds. The egress carries identity the gate already trusts.
A signed record for every access.
Local traffic stays local. Every access leaves a signed, non-repudiable record - who, where, on whose authority, under what legal basis, on what date.
No more shadow infrastructure.
Replace shadow proxy networks and residential SDK pools with verified, attributable infrastructure. No abuse complaints chasing your security team. No data residency surprises. Every access has a paper trail your legal team can defend.
Independent infrastructure, not a walled garden.
Metro Fabric isn't a CDN, a hyperscaler, or a content network. It's neutral infrastructure built on published standards - so anyone can read our credentials, no integration partner gets a privileged seat, and you don't get tied to a single stack.
- 01 / 03 - Position
Vendor neutral.
Not a CDN, not a hyperscaler, not a publisher. Independent of any single stack and aligned with no integration partner above another.
- 02 / 03 - Protocol
Open standards.
Built on RFC 9421 (HTTP Message Signatures) and IETF web-bot-auth. No proprietary protocol; any standards-compliant verifier can validate our credentials.
- 03 / 03 - Portability
No lock-in.
Portable identity. Standards-compliant verification anywhere it's accepted. Your KYC, your record, your credential - yours to take with you.
Identity is the next infrastructure primitive.
The agentic web is not waiting for permission. The question is whether it has trust infrastructure or doesn't. Metro Fabric is building that infrastructure - neutral, standards-aligned, edge-verified.