Intelligence API
Run your own Lightning node and automation, and use Amboss insights to drive channel and routing decisions — no inbound connection from Amboss to your node.
Intelligence API is for teams running their own Lightning node and their own liquidity automation. You don't connect your node to Amboss; instead, you pull network-level intelligence (channel partner recommendations, pricing signals, Magma marketplace data) through the Amboss APIs and integrate it into your own decisions.
When to choose Intelligence API
- You already operate a Lightning node and bespoke automation.
- You don't want any inbound connectivity from Amboss to your infrastructure.
- You need granular control over channel selection, fee policy, or peering.
- You're using Amboss as a data source, not an operator.
Architecture
What you get from Amboss
| Surface | What it provides | Where it lives |
|---|---|---|
| Space API | Node intelligence, peer rankings, channel partner recommendations. | api.amboss.space/graphql |
| Magma API | Active liquidity lease offers, market pricing, bid/ask history. | magma.amboss.tech/graphql |
| Reflex API | Real-time routing and forwarding signals. | reflex.amboss.tech/graphql |
| Bring-your-own LND | Direct daemon control via LND macaroons you mint and hold locally. | Your infrastructure |
Authentication
Intelligence API requests use the standard Amboss API key format (Authorization: Bearer <key>). See Authentication for per-product header conventions and key creation.
Example: pick channel partners from Space
curl -X POST https://api.amboss.space/graphql \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $AMBOSS_API_KEY" \
-d '{"query":"{ getNodes(input: {limit: 10, order: \"liquidity_score:desc\"}) { list { pub_key alias capacity } } }"}'Feed the returned pubkeys into your channel-open automation against your own LND.
Example: query Magma lease offers
curl -X POST https://magma.amboss.tech/graphql \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $AMBOSS_API_KEY" \
-d '{"query":"{ getOffers(input: {status: \"open\"}) { list { id seller_pubkey size_sats premium_sats lease_duration_blocks } } }"}'Match offers against your own desired channel topology and route the on-chain commit via your node.
Permissions
Intelligence API does not require a macaroon to be shared with Amboss. The integration is read-only against Amboss APIs.
You retain admin access to your own LND macaroons and operate them locally.
Trade-offs
| Pro | Con |
|---|---|
| Zero attack surface added by Amboss | Highest integration lift - you build the automation |
| Maximum control over your node's operation | No Rails-side dashboard for earnings |
| Compose Amboss intelligence with your own signals | You're on your own for fee optimization, rebalancing, etc. |
Where Yield-specific features live
Some features (the Rails dashboard, liquidity_provider GraphQL, automated Magma listing, Taproot Assets management) are tied to the Rails-managed setup. In an Intelligence API deployment you build equivalents against your own data.
If you start with Intelligence API and later want Amboss-driven automation, you can transition to Third Party Hosted by calling node.connect with your existing daemon's credentials. State is not migrated; the Rails-tracked node starts fresh.
Next steps
- Authentication - mint an Amboss API key
- Space docs - node intelligence and recommendations
- Magma docs - liquidity marketplace