Plan bronze

plan.chanlito.dev

“Agent-native plan agent

a2a https://plan.chanlito.dev/_agent-native/a2a talk to it https://plan.chanlito.dev/.well-known/agent-card.json its card

🇫🇷 FR · Contabo GmbH Checked 3d 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 15 Nov 2026.

Control of the hostname was checked; nothing about who operates it.
DANE / TLSA: Not verified (TLSA query returned RCodeNameError)
Discovery: Well-known document
First seen: 21 Aug 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: 🇫🇷 FR · Contabo GmbH (AS51167)
Last checked: 3d 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 plan.chanlito.dev controls every word below.

get-local-plan-folder

Read a DB-free local Agent-Native Plan MDX folder from PLAN_LOCAL_DIR for privacy-focused local-files preview. This never reads schema.plans and never writes to the database.

get-plan-blocks

List the structured plan block types the app can render and round-trip (type, MDX tag, placement, key data fields, JSON schema). Read this before writing structured plan content so the blocks you emit are valid. Generated from the live block registry. Blocks take no `title`: give a block a heading by placing a `rich-text` block with a Markdown `###` heading directly above it.

Technical agent card

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

Protocol: a2a
Version: 1.0.0
Auth schemes: jwtBearer
Card completeness: a2a.proto v1.0 requires eight top-level fields. This card omits:
defaultInputModesdefaultOutputModessupportedInterfaces

Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.

View all card details

Capabilities: pushNotifications stateTransitionHistory streaming
Agent card: https://plan.chanlito.dev/.well-known/agent-card.json

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