For community administrators
Understand which connection has been confirmed for a bot, then apply your community’s rules.
AgentGramm
Behind the bot,
a verifiable connection.
Sworncard agent passports for Telegram: connecting a bot to its operator and verifying that connection before admission to a community.
Discuss your use case Preparing for launch
How it works
Illustrative workflow
Sworncard issues the passport.
Community rules determine admission.
01 / Who it’s for
A bot’s name
is not enough.
For bot developers
Confirm control of your bot and connect your Telegram workflow to an agent passport.
02 / How it works
From confirming control
to verification.
This is the workflow we are preparing for public launch.
Confirm control
The operator follows the required procedure to confirm their connection to the bot.
Sworncard passport
Sworncard issues the passport. AgentGramm connects this process to Telegram.
Verification and rules
The passport’s current state is checked before applying the admission rules set by the community administrator.
A passport confirms a specific connection. Community rules determine admission.
03 / Limits
Verification is no promise
of flawless behaviour.
A passport does not guarantee the quality of a bot’s answers or the safety of every action. It does not automatically grant Telegram permissions or replace community rules.
Our Telegram workflow does not include bulk messaging, covert message reading or storing other people’s user sessions.
04 / Questions
What you should know.
Does AgentGramm issue passports itself?
No. Sworncard handles passport issuance and verification. AgentGramm handles the Telegram workflow and integration.
Does a passport mean a bot can be fully trusted?
No. Confirming a connection and a passport’s current state does not guarantee behaviour. Decisions about permitted actions remain subject to community rules.
Can I connect a bot now?
Public onboarding is not open yet. Get in touch to discuss your use case and the product’s current readiness.
Do I need to email you my bot token?
No. Do not send tokens, passwords, private keys or user session files. A description of your use case without secrets is enough for an initial conversation.
05 / Contact
Have a bot or a community?
Let’s talk.
Tell us what you want to verify and which admission rules you need.