Lumeo sits alongside your website, ERP, catalogs, and sales workflows. People keep the visual experience they know; AI agents receive a structured, current, and policy-controlled interface.
Human website unaffectedFirst-party sources onlyActions remain approval-controlled
Gateway
One control plane
Sources
Interfaces
Policy
Proof
one verified domain · one operating model
The request path
What happens when an agent asks your business a question?
Lumeo turns an open-ended machine request into a traceable five-step lifecycle. Select a step to inspect the request, the control applied, and the operational result.
Request lifecycle
STEP 01 / 05Illustrative request
Agent identifies the business
An AI agent discovers the approved machine interface through the business domain, its UCP profile, or its llms.txt manifest.
Operational result: The agent finds one canonical entry point instead of guessing across pages and PDFs.
Platform architecture
Four layers. One controlled operating model.
Start with the layer that solves today’s constraint. Together, the four layers keep discovery, data quality, execution, and accountability tied to the same verified business domain.
01
Build the data twin
Ingestion & source layer
Connect public pages, engineering documents, catalog files, and systems of record into one reconciled business model.
Scheduled crawling and change detection
Website, PDF, CSV, ERP, and PIM reconciliation
Fact-level provenance, timestamps, and authority rules
02
Publish once
Multi-protocol interface layer
Expose the same canonical model through the machine interfaces agents already know how to discover and invoke.
Automated llms.txt and full Markdown context
MCP tools for search, product detail, and RFQs
UCP discovery profile on the verified business domain
03
Keep the business in control
Policy & control layer
Define which agents may read, query, or execute. Sensitive sales actions can pause for a human decision before anything becomes binding.
Asynchronous RFQ approval inbox
Email, webhook, and CRM handoffs
Client scopes, rate limits, and action-risk classes
04
Make every response inspectable
Integrity, terms & metering layer
Attach freshness, commercial terms, attribution, and verifiable proof to each response while measuring machine access as an operational channel.
TTL, valid-until, binding status, and MOQ terms
Ed25519 response signatures and content digests
Usage ledger with optional x402 and HTTP 402 adapters
Gateway console & telemetry
Measure the machine channel like an operating system—not a page-view report.
See what agents request, where your information fails them, which sources are current, and where a person needs to complete the commercial handshake.
ACME Gateway
Illustrative workspace · last 30 days
Gateway healthy
Quoted demand
€112,400
this month
Reconciliation health
99.8%
4 conflicts flagged
Tool invocations
14,210
agent requests
Edge response
42 ms
average latency
Source freshness
The inputs behind every published fact
Product catalog.pdf
Checked 8 min ago
Current
Website pages
126 facts published
Current
ERP inventory
Sync every 60 seconds
Live
Human RFQ pipeline
Commercial actions awaiting or completing review
14
Draft
6
Review
31
Signed
3 quotes need a sales decision
Freight, discount, or binding terms require review.
Unanswered agent queries
“RoHS certificate for AX-104” and 18 other searches reveal catalog gaps before sales loses the conversation.
Agent identity breakdown
Understand demand from public assistants, buyer agents, search systems, and approved enterprise clients without exposing private credentials.
Console values shown above are illustrative. Your workspace reports observed traffic, configured sources, and actual approval states.
Make your infrastructure agent-ready
Start with the information agents can see today.
Run a readiness scan for the public website, or schedule a technical review when catalogs, APIs, and systems of record are already in scope.