Orca Scheduling Agent bronze

api.fluffymane.com

“A2A-compatible scheduling transport for Orca meeting coordination.

a2a https://api.fluffymane.com/api/v1/a2a talk to it https://api.fluffymane.com/.well-known/agent-card.json its card

✓ 🇺🇸 US · Railway ✓ Checked 5d ago “ pushNotifications, streaming

✓ 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 Let's Encrypt domain-validated

Valid until 16 Jan 2027 as of our check on 9 Nov 2026.

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

Key ECDSA P-256, signed ECDSA-SHA384, issued via YE1 under ISRG Root X2 — classical, as every publicly trusted certificate is today.

Names on this certificate (1)

api.fluffymane.com.

Connection

TLS 1.3 · X25519 — classical 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

First seen

1 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 api.fluffymane.com controls every word below.

Technical agent card

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

Protocol

a2a

Version

0.1

Auth schemes

bearerAuth

Card completeness

a2a.proto v1.0 requires eight top-level fields. This card omits:

supportedInterfaces

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

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