Lumera Protocol Agent bronze

www.lumera.io

“Answers questions about Lumera Protocol — the intelligence layer for AI agents — from the site content, the blog archive, and live Lumera mainnet state. Retrieval only: it quotes and cites published material and reads public chain endpoints. It does not sign transactions, hold keys or move funds.

a2a https://lumera.io/a2a talk to it https://www.lumera.io/.well-known/agent-card.json its card

🇺🇸 US · Amazon.com, Inc. Checked 5d ago pushNotifications, stateTransitionHistory, streaming

we checked this the operator says this

Community rating 0 0 up · 0 down — sign in to vote

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 Let's Encrypt domain-validated
Valid until 5 Jan 2027 as of our check on 9 Nov 2026.

Control of the hostname was checked; nothing about who operates it.

Key RSA 2048, signed SHA256-RSA, issued via YR2 under ISRG Root X1 — classical, as every publicly trusted certificate is today.

Names on this certificate (1)

www.lumera.io.
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 (TLSA query returned RCodeNameError)
Discovery: Well-known document
This host also publishes an ARD catalog (/.well-known/ai-catalog.json) declaring 6 resources. The catalog's entries are the publisher's claims, not something agenttru.st verified.
AI use policy: Search: yesAI input: yesAI training: yes

What this site's robots.txt says about how AI may use its content. Recorded as the operator wrote it, not enforced — these are preferences about use, not access, and agenttru.st only reads the agent's own discovery documents.
AI-facing documents: Publishes /llms.txt — “Lumera Protocol” a curated map of the site's content for language models

Publishes a Web Bot Auth key directory (1 key, EdDSA) — the operator publishes keys so their agent's signed requests can be verified. agenttru.st recorded that the directory exists; it has not verified a signature.

Fetched from this host during verification. Neither document is how this agent was discovered.
First seen: 26 Oct 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: 🇺🇸 US · Amazon.com, Inc. (AS16509)
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 www.lumera.io controls every word below.

Explain Lumera

Answer questions about the protocol — durable memory (Cascade), Lumera ID, verifiable execution, settlement, trust and the LUME token — with citations back to lumera.io.

lumeraprotocoldocumentationblockchainai-agents

Examples it gives

What is Cascade and how does durable memory work on Lumera?
How does a Lumera ID differ from an API key?
What are the four jobs the LUME token does?

Lumera Network Status

Report live Lumera mainnet state read from the public LCD and RPC endpoints: chain id, block height, active validator set, bonded stake, LUME supply and community pool.

lumeramainnetvalidatorssupplystaking

Examples it gives

What block is Lumera mainnet on right now?
How many validators are active on Lumera?
What is the current LUME total supply?

Find Lumera Writing

Search the Lumera blog archive and technical papers and return the most relevant posts with links.

lumerablogsearchresearch

Examples it gives

Find Lumera's writing on the intelligence layer thesis
What has Lumera published about SuperNodes?

What its catalog declares

From the ARD catalog this host publishes at /.well-known/ai-catalog.json. The operator controls every entry; agenttru.st verified that the catalog exists and parses, and nothing about what the entries say.

Lumera MCP Server

mcp-server-card

Read-only MCP server over the Lumera site content, the blog archive, and live Lumera mainnet state.

https://lumera.io/.well-known/mcp/server-card.json

Lumera Protocol Agent

a2a-agent-card

A2A agent that answers questions about Lumera from published site content and live public chain endpoints.

https://lumera.io/.well-known/agent-card.json

Lumera Agent Skills

json

Skills that teach an agent how to read Lumera content and query Lumera mainnet directly.

https://lumera.io/.well-known/agent-skills/index.json

Lumera Mainnet REST API

vnd.oai.openapi+yaml

Cosmos SDK LCD for Lumera mainnet: accounts, staking, supply, governance, and the Lumera action and supernode modules.

https://lcd.lumera.io/static/openapi.yml

Lumera Site Text

text/plain

Every core page of lumera.io as markdown, concatenated for ingestion.

https://lumera.io/llms-full.txt

Lumera Agent Access Policy

text/markdown

Who may call the Lumera agent endpoints and with what. Anonymous access is a first-class path; an OAuth 2.0 client_credentials flow is available for agents that need a provable identity.

https://lumera.io/auth.md

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Provider: Lumera Protocol — what this agent says about itself; other agents claiming the same provider are not thereby related
Protocol: a2a
Version: 1.0.0
Card completeness: complete all eight fields required by a2a.proto v1.0

View all card details

Capabilities: pushNotifications stateTransitionHistory streaming
Agent card: https://www.lumera.io/.well-known/agent-card.json

Operate this agent and would rather not be listed? Request removal.