Odile Gate by Odile Labs bronze

gate.odilelabs.com

“Odile Gate, from Odile Labs (communication infrastructure connecting people, businesses and AI agents), puts a key, an allow-list, a rate limit and an audit log in front of an HTTP API. 1) gate_create_project with the API base URL; save the admin_key in the project .env (gitignored), never in code. 2) gate_create_app once per app, listing only the calls that app makes (from the client code you wrote). 3) Point the app at the gateway URL with Authorization: Bearer <app key>; first test an allowed call and a forbidden method (403 route_not_allowed). 4) gate_audit shows what each app did; gate_explain_refusal explains a refused call. Gate Actions: for an agent that changes customer data, gate_create_run grants one session narrow, expiring permission (scope, limits, approvals); gate_set_app_runs makes runs mandatory. Before handing an integration production access, use gate_check_setup to show the human actual protection settings, configuration gaps and exact remedies. It is read-only configuration analysis, not

https://gate.odilelabs.com/mcp its card

✓ Checked 6d ago “ tools

✓ we checked this   “ the operator says this

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 Google Trust Services domain-validated

Valid until 17 Jan 2027 as of our check on 9 Nov 2026. A wildcard certificate: its other hosts are invisible here, because CT logs the wildcard, not them.

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

Key ECDSA P-256, signed ECDSA-SHA256, issued via WE1 under GTS Root R4 — classical, as every publicly trusted certificate is today.

Names on this certificate (3)

odilelabs.com, gate.odilelabs.com, *.gate.odilelabs.com.

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

Discovery

Well-known document

This host also publishes an ARD catalog (/.well-known/ai-catalog.json) declaring 1 resource. 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 — “Odile Gate” a curated map of the site's content for language models

Fetched from this host during verification. Neither document is how this agent was discovered.

First seen

2 Nov 2026

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 gate.odilelabs.com controls every word below.

This card declares no skills. That is not a fault — the field is optional, and an agent can be perfectly functional without describing itself.

What kind of listing

• No skills declared: Its card declares no skills, or, for an MCP server, listed no tools.

Checked by agenttru.st against this listing's hostname and card — facts about a name or an address, not about what the agent does. How kinds are decided.

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.

Technical agent card

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

Protocol

mcp

Version

1.8.0

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