Finch bronze
developer.tryfinch.com
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 15 Jan 2027 as of our check on 15 Nov 2026.Control of the hostname was checked; nothing about who operates it.Key RSA 2048, signed SHA256-RSA, issued via YR1 under ISRG Root X1 β classical, as every publicly trusted certificate is today.
Names on this certificate (1)
developer.tryfinch.com. - Connection
- TLS 1.3 Β· X25519MLKEM768 β post-quantum hybrid key exchange, agreed with our checker on 15 Nov 2026. What this means
- DANE / TLSA
- Not verified
- Discovery
- Well-known document
- AI use policy
-
What this site's
robots.txtsays 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β “Finch” a curated map of the site's content for language modelsFetched from this host during verification. Neither document is how this agent was discovered. - First seen
- 17 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
- 7h 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 developer.tryfinch.com controls every word below.
finch-integration-audit
Guide developers through auditing an existing Finch integration β discovering what's actually implemented across backend and frontend, checking it against Finch Connect flow, token/reauthentication handling, scope coverage, webhooks, and best practices, and producing a severity-rated findings report. Use when a developer has an existing Finch integration and wants it reviewed for missing features, deprecated patterns, or incorrect implementation β not for building a new integration from scratch.
finch-integration-backend
Guide developers through building the backend of a Finch integration β Finch Connect session creation, authorization code exchange, access token management, Finch API calls, data persistence, reauthentication handling, and tests. Use when a developer is building the server-side portion of a new application, adding Finch to an existing application, or extending an already-integrated connection with a new product scope or entity β not when Finch is already integrated and a feature like reauthentication isn't working correctly; that's the Finch Integration Audit skill's job.
finch-integration-frontend
Guide developers through building the frontend of a Finch integration β installing the Finch Connect SDK, launching an embedded Connect session or redirect flow, handling the authorization code callback, and surfacing reauthentication prompts to employers. Use when a developer is building the client-side portion of a Finch integration β not when Finch is already integrated and a feature like the reauthentication prompt isn't working correctly; that's the Finch Integration Audit skill's job.
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- Finch β what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 1.0.0
- Card completeness
-
a2a.proto v1.0 requires eight top-level fields. This card omits:
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 streaming
- Agent card
- https://developer.tryfinch.com/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.