Albato Copilot bronze
copilot.aws-us-east-2.albato.com
“Albato Copilot builds and manages Albato automations (bundles) on behalf of an Albato user: it finds apps, triggers and actions, wires connections, maps fields, validates and starts the bundle, and answers product questions from the Albato knowledge base. Authentication — every request needs BOTH headers: `X-Copilot-Partner-Token` (issued by Albato to the embedded partner whose agent is calling) and `Authorization: Bearer <Albato user JWT>` (the end user the Copilot acts for — the same token the Albato UI uses). Send `A2A-Version: 1.0`. Conversation — keep `contextId` across messages to continue the same session. The Copilot may pause a task in TASK_STATE_INPUT_REQUIRED to ask a question or to offer options; the status message then carries a DataPart {"type": "hitl_request", "options": [...]}. Answer in a new message with the same `taskId` and `contextId`: plain text for a question, and for options the `option_id` / label or a DataPart {"selected_option_id": "..."}. A `connection_url` in that DataPart
https://copilot.aws-us-east-2.albato.com/.well-known/agent-card.json its cardwe 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 22 Jan 2027 as of our check on 12 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)
copilot.aws-us-east-2.albato.com. - Connection
- TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 12 Nov 2026. What this means
- DANE / TLSA
- Not verified
- Discovery
- Well-known document
- First seen
- 12 Nov 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
- 2d 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 copilot.aws-us-east-2.albato.com controls every word below.
Build an Albato automation
Create, configure, validate and start an Albato bundle end-to-end: pick the apps, the trigger and actions, choose or add connections, map fields, set filters, check and launch.
- Create an automation: new Typeform response -> row in Google Sheets
- Сделай связку: новый лид в amoCRM -> сообщение в Telegram
Find apps, triggers and actions
Look up which apps Albato integrates, which triggers and actions they offer, and which connections (credentials) the user already has.
- Which triggers does HubSpot have?
- Есть ли интеграция с Bitrix24 и какие у неё действия?
Inspect or diagnose an existing automation
Read an existing bundle, explain its steps and check why it is not running.
- Why is my automation 123 not running?
- Проверь связку 456
Ask about Albato
Product and how-to questions answered from the Albato knowledge base.
- How does Albato bill operations?
- Как подключить Google Sheets к Albato?
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- Albato — what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 1.0.0
- Auth schemes
- albatoUser partnerToken
- Card completeness
- complete all eight fields required by a2a.proto v1.0
View all card details
- Capabilities
- extendedAgentCard pushNotifications streaming
- Agent card
- https://copilot.aws-us-east-2.albato.com/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.