The motivation was partly selfish. I run domain and infosec lookups constantly and wanted them on my phone. It turned out to be the lowest friction entry point into ArkAPI. Easier to say "message the bot".

Each Telegram user gets their own private session. Hit 

, and start querying. No signup, no API keys. Both payment rails, Ark and Lightning, are fully working on Signet. Receipts show which one funded your session.

 (Ark address + Lightning invoice + QR), 

Every response shows cost and remaining balance, so the pay-per-call model is visible with each query.

This is all running on signet via Second's Bark stack. No separate Lightning node.

security

bitdevs

devs

lightning

ArkAPI has a Telegram client now: [@ArkAPI_bot](https://t.me/ArkAPI_bot)

The motivation was partly selfish. I run domain and infosec lookups constantly and wanted them on my phone. It turned out to be the lowest friction entry point into ArkAPI. Easier to say "message the bot".

Each Telegram user gets their own private session. Hit `/fund`, get some starter signet sats from [arkfaucet.com](https://arkfaucet.com), and start querying. No signup, no API keys. Both payment rails, Ark and Lightning, are fully working on Signet. Receipts show which one funded your session.

Full command list:

**Session:** `/fund` (Ark address + Lightning invoice + QR), `/balance`, `/activity`

**Bitcoin:** `/price`, `/whale`, `/news`

**AI:** `/chat`, `/image`, `/summarize`

**OSINT:** `/domain`, `/dns`, `/whois`, `/ssl`, `/headers`, `/ip`

**Utility + Web:** `/weather`, `/translate`, `/paste`, `/markdown`, `/qr`, `/screenshot`, `/markets`

Every response shows cost and remaining balance, so the pay-per-call model is visible with each query.

This is all running on signet via Second's Bark stack. No separate Lightning node.

Try it: [t.me/ArkAPI_bot](https://t.me/ArkAPI_bot) Landing page: [arkapi.dev/telegram-bot](https://arkapi.dev/telegram-bot/)