Skip to main content
Nebula exposes its capabilities as a set of named tools delivered over the Model Context Protocol (MCP). When an AI agent connects to Nebula, it discovers these tools automatically and can call them in natural conversation. Every tool call travels through the Nebula Hub at https://nebulaonchain.xyz, which enforces your spending policy, obtains human confirmation when required, and submits signed transactions to the Stellar network on the agent’s behalf.

Tool call anatomy

An agent invokes a tool by name and passes a JSON object whose keys match that tool’s parameter schema. No special client code is needed — any MCP-compatible runtime (Claude Desktop, a custom agent loop, etc.) handles the wire protocol automatically. Each reference page in this section documents:
  • Description — what the tool does and when to use it
  • Parameters — the exact fields the tool accepts, their types, and whether they are required
  • Response — the fields returned on success, and any special status codes
  • Examples — a ready-to-copy call and response pair

Response structure

Every Nebula tool response is a JSON object that always includes a top-level status field. The possible values are:
StatusMeaning
okThe tool completed successfully. Data is in the data field; a human-readable summary is in message.
errorThe tool failed. The reason field explains what went wrong.
confirmation_requiredThe Hub has paused the action pending human approval. The confirmation_id field identifies the pending request; call await_confirmation to resume.
rejectedA pending confirmation was denied by the human approver. The action was not taken.

All tools by category

Wallet

Core wallet operations: health checks, address lookup, balance queries, transfers, and funding.
ToolSummary
pingHealth check — confirms tools are reachable
get_addressReturn the agent’s Stellar G… address
check_balanceView XLM and USDC balances
transferSend XLM to any Stellar address
request_fundingGet instructions to fund the wallet

Payments

HTTP-native payments via the x402 protocol and metered pay-per-use sessions via MPP.
ToolSummary
x402_fetchFetch a URL, paying the x402 toll automatically
x402_payPay an x402 payment request directly
mpp_open_sessionOpen a metered-payment session
mpp_fetchFetch content within an active MPP session
mpp_statusCheck the balance and status of an MPP session
mpp_close_sessionClose an MPP session and settle the balance

Treasury

Earn yield on idle funds, monitor balances, and review spending history.
ToolSummary
blend_check_ratesQuery current Blend Protocol lending rates
get_treasury_statusView treasury allocation and yield earned
spending_reportRetrieve a spending summary for a time period

Policy & Identity

Inspect spending limits, wait for human approval, and manage on-chain identity.
ToolSummary
get_policy_statusRead the current policy limits and usage
await_confirmationPoll for the result of a pending confirmation
register_identityRegister a domain or handle as your on-chain identity
get_my_reputationRead the reputation score for an identity

Dashboard-only tools

The following tools are available exclusively through the Nebula dashboard UI. They are not accessible to agent tokens via MCP, because they involve privileged configuration actions that should be performed by a human owner:
ToolPurpose
set_policy_limitsConfigure per-transaction and daily spending caps
deploy_policyPublish a new policy on-chain
blend_depositDeposit funds into Blend Protocol for yield
blend_withdrawWithdraw funds from Blend Protocol
optimize_treasuryAuto-rebalance treasury allocations
set_liquidity_thresholdSet the minimum liquid XLM balance to maintain
Log in to your dashboard at nebulaonchain.xyz to configure these settings.

Calling tools directly over HTTP

Advanced users can bypass MCP and call the Hub’s tool API directly. This is useful for server-side integrations or testing. Endpoint: POST https://nebulaonchain.xyz/api/tools/{toolname} Headers:
Authorization: Bearer nbl_live_…
Content-Type: application/json
Body: A JSON object matching the tool’s parameter schema. Example — calling check_balance directly:
curl -X POST https://nebulaonchain.xyz/api/tools/check_balance \
  -H "Authorization: Bearer nbl_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'
The response shape is identical to what MCP agents receive — the same status field and data object documented on each tool’s reference page.