Acinq
ACINQ is a Paris-based Bitcoin technology company and one of the principal implementers of the Lightning Network. It builds and maintains eclair, a Scala Lightning node with a 56-method JSON/HTTP API used for routing and channel management at scale; phoenixd, a self-custodial Lightning server daemon that exposes a 27-endpoint HTTP API plus websocket and HMAC-signed webhooks for merchants and applications; the Phoenix self-custodial mobile wallet; and the Kotlin Multiplatform libraries lightning-kmp, bitcoin-kmp and secp256k1-kmp published to Maven Central. ACINQ also operates its own mainnet and testnet Lightning nodes and acts as a liquidity service provider. Every API is self-hosted software rather than a vendor-hosted SaaS endpoint.
Acinq publishes 2 APIs on the APIs.io network. Tagged areas include Company, Blockchain, Bitcoin, Lightning Network, and Payments.
The Acinq catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Acinq’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, pricing, changelog, and 23 more developer resources.
Kin Score
APIs 2
Individual APIs this provider publishes, each with its own machine-readable definition.
phoenixd HTTP API
The HTTP API of phoenixd, ACINQ's self-custodial Lightning server daemon. 27 documented endpoints covering Bolt11 invoices, Bolt12 offers, Lightning addresses, on-chain sends an...
Eclair JSON API
The JSON/HTTP API of eclair, ACINQ's Scala implementation of the Lightning Network. 56 documented methods grouped into node info, connections, channel open/close/splice/RBF, pee...
Pricing Plans 1
Published pricing tiers and plan structures.
Acinq Plans Pricing
PLANSRate Limits 1
Documented rate limits and quota policies.
Acinq Rate Limits
RATE LIMITSEvent Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Acinq Phoenixd Webhooks
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.