← Back to Skills Marketplace

Maestro Api

Name: Maestro Api
Author: vardominator

by Varderes · GitHub ↗ · v0.2.4 · MIT-0

cross-platform ⚠ suspicious

1729

Downloads

Stars

Active Installs

Versions

Install in OpenClaw

/install maestro-skill

Description

Query Maestro APIs over HTTP using the SIWX + JWT + x402 credit purchase flow. Resolve the exact endpoint from docs.gomaestro.org before requesting or paying.

README (SKILL.md)

Maestro API

Use this skill when the user wants a direct HTTP call to a Maestro endpoint. The intended path is short: resolve the exact operation page, send the real request, satisfy the live SIWX challenge, and only buy credits if the server still returns 402.

Fast Path

Resolve the exact operation page in docs.gomaestro.org.
Read the page's .md form and use its OpenAPI block as the source of truth.
Build the request URL from servers: plus the operation path.
Send the real request with no auth or payment headers.
If the response is 200, return the data.
If the response is 402 with extensions.sign-in-with-x, sign the SIWX challenge and retry the exact same request with sign-in-with-x.
If that retry returns 200, return the data.
If that retry returns 402 plus Authorization: Bearer \x3Cjwt>, buy credits from the latest accepts[] entry and retry the exact same request with Authorization and X-PAYMENT.
Reuse the JWT for follow-up queries until it expires or Maestro asks for more credits.

Resolve Endpoint From Docs

Use docs only to find the exact operation page. Do not browse broadly once you have it.

Start with https://docs.gomaestro.org/llms.txt only if the operation page is not already obvious.
Prefer operation pages over quick-start pages.
Read the .md page and extract:
- operation line -> path
- servers: -> base URL for the chosen network
- parameters and body schema -> request shape
Combine server.url + path.
Do not derive the REST host from the SIWX domain or URI.
Useful Bitcoin routing shortcuts:
- confirmed chain data -> Blockchain Indexer API
- mempool-aware or pending data -> Mempool Monitoring API
- mempool.space-style routes -> Esplora API
- wallet balances or wallet activity -> Wallet API

Minimal Prerequisites

Ask only for what is required to sign and pay:

PRIVATE_KEY, or a runtime CDP wallet signer
enough USDC and native gas on one network from the live 402 response
no API key

Request Rules

Keep method, path, query parameters, and body unchanged across the unauthenticated request, the SIWX retry, and the paid retry.
Always use the latest 402 response for supported_chains, accepts[], asset, pay_to, and price limits.
Confirm before the first paid mainnet request.
If a paid retry still fails, report:
- docs page used
- selected network
- selected amount
- signer address
- minimal next action

Read Only When Needed

Read SIWX + x402 Reference only when you need the exact signing or header details:

sign-in-with-x payload format
X-PAYMENT payload format
EIP-4361 SIWX message template
ERC-3009 EIP-712 domain and message fields
response header meanings
failure cases and common pitfalls

Usage Guidance

This skill performs real Maestro API calls and may ask you to sign messages and pay on-chain. Before using it: (1) do not paste a long‑term private key into a chat prompt — prefer a hardware or external signer or an ephemeral/test key; (2) demand explicit, human confirmation before any mainnet payment (network, pay_to address, amount in USDC atomic units, and the docs page used); (3) test on a non‑mainnet network first; (4) verify docs.gomaestro.org is the correct official docs URL and confirm the operation page it resolved; (5) consider using a wallet that can produce signatures without exposing raw private key material (browser wallet, HSM, or wallet-connect flow). The skill's registry metadata lacks declared credentials and has no homepage or source, so you should be cautious about trusting it with real funds or private keys.

Capability Analysis

Type: OpenClaw Skill Name: maestro-skill Version: 0.2.4 The skill facilitates automated interaction with the Maestro API, requiring the agent to handle a `PRIVATE_KEY` for Sign-In-With-Ethereum (SIWX) authentication and EIP-712 transaction signing to purchase API credits using USDC. While these actions are consistent with the stated purpose in SKILL.md and the technical reference in references/siwx-x402.md, the requirement for raw private key access and the logic for automated financial transfers present a high security risk without further sandboxing or hardware-backed signing constraints.

Capability Assessment

ℹ Purpose & Capability

The skill's name and description match the runtime instructions: resolving docs.gomaestro.org, performing unauthenticated requests, doing SIWX authentication, and buying credits via the x402 flow. Asking for a wallet signer and funds is coherent with the stated purpose. Minor concern: the package metadata declares no required environment variables or primary credential even though the SKILL.md explicitly says the agent will need a PRIVATE_KEY or a runtime wallet signer and on-chain funds.

✓ Instruction Scope

SKILL.md is narrowly scoped to resolving an operation page in docs.gomaestro.org, issuing the HTTP request, handling 402/SIWX/JWT flows, and performing the specified payment retry. It does not instruct broad system scanning or exfiltration, and it contains concrete steps (confirm before first paid mainnet request). The instructions do ask the agent to perform signing and to send payment headers and JWTs — exactly what this API requires.

✓ Install Mechanism

No install spec and no code files — instruction-only skill. This reduces disk-write/remote-code risks; there are no external downloads or package installs to review.

⚠ Credentials

The functional flow requires a signing capability (PRIVATE_KEY or runtime CDP wallet signer) and on-chain funds (USDC + gas). That is proportionate to making paid Maestro requests, but those are highly sensitive credentials. The skill's metadata lists no required env vars or primary credential, so there's a mismatch between what it will need at runtime and what is declared in the registry. Because the agent will be asked to sign EIP-191 and EIP-712 messages and potentially submit payments, users should not paste long‑term private keys into prompts; a hardware/external signer, ephemeral key, or explicit gating is recommended.

✓ Persistence & Privilege

The skill does not request always:true, has no special OS or install privileges, and does not modify other skills. Model invocation is allowed (normal). Nothing in the files requests persistent agent-level changes.

How to Use

Make sure OpenClaw is installed (local or Docker)
Run the install command in chat: /install maestro-skill
After installation, invoke the skill by name or use /maestro-skill
Provide required inputs per the skill's parameter spec and get structured output

Version History

v0.2.4

- Renamed skill from "maestro-bitcoin" to "maestro-api" to clarify broader API support. - Simplified and streamlined the client interaction flow; now emphasizes a fast step-by-step path for querying Maestro endpoints. - All details about signing, payment, and headers are now centralized in a separate reference file (`references/siwx-x402.md`). - Clarifies that the endpoint base URL and path come only from the docs operation page—not the SIWX challenge. - Workflow now strictly reuses the latest 402 response for payment parameters and minimizes user prompts. - Improved doc navigation guidance and removed extraneous boilerplate.

v0.2.3

- API endpoint URL logic improved: now resolve the correct Maestro REST base URL from https://docs.gomaestro.org instead of assuming api.gomaestro.org for API requests. - Clarified distinction between authentication domains (used in SIWX messages) and actual API endpoint hosts—never guess the request URL from SIWX challenge fields. - Added tables of live-supported blockchains and documented their specific REST base URLs for Bitcoin, Cardano, and Dogecoin. - Updated documentation references and quickstart links for easier integration. - No logic or protocol changes to SIWX + JWT + x402 flow; all payment and authentication steps remain unchanged.

v0.2.2

**Changelog for version 0.2.2 of maestro-skill:** - Major rewrite and clarification of SKILL.md documentation. - Refined the end-to-end SIWX + x402 + JWT flow, specifying exact challenge/response details and payload structures. - Added detailed, step-by-step guides and example payloads for EIP-4361, EIP-191, and ERC-3009 handling. - Clearly documented chain ID formatting requirements (CAIP-2), header formats (with base64 and string fields), and common pitfalls. - Removed network default/fallback logic and clarified that all choices must be made from live challenge responses. - Improved explanation of headers, credit purchase rules, response scenarios, and outlined all necessary prerequisites.

v0.2.1

- Updates credit purchase policy: allows arbitrary purchase amounts within a minimum of $0.10 and maximum of $50.00, rather than just fixed tiers. - Documents base credit cost as $0.000025 per credit. - Revises instructions to choose a purchase amount within allowed bounds rather than requiring selection of a fixed tier. - Clarifies header handling, funding requirements, and network selection rules for improved user guidance.

v0.2.0

**Changelog for maestro-skill v0.2.0** - Major update: x402 flow rewritten to use SIWX + JWT + credit purchase process, replacing previous direct payment approach. - Updated client interaction: Now requires SIWX (`Sign-In-With-X`) authentication, JWT sessions, and credit pre-purchase in fixed tiers. - Clearly documents accepted credit tiers for purchase, minimum and maximum limits, and new header requirements. - Workflow, prerequisites, and agent rules revised to reflect the credit model and JWT+SIWX flows. - Network selection, funding guidance, and explorer link examples improved for clarity and testnet/mainnet coverage. - Documentation rewritten to match current Maestro Bitcoin API expectations and client SDK flow.

v0.1.7

**Major update: Refined wallet requirements, default network selection, and added CDP Agent Wallet support.** - Default production network is now Ethereum mainnet (`eip155:1`); Base mainnet used only if user requests or approves. - Explicit support for both `PRIVATE_KEY` signer and Coinbase CDP Agent Wallet; ask for only minimally required wallet prerequisites. - Enhanced workflow with clear guidance for selecting payment network and constructing explorer links for transaction lookup. - Updated agent rules: never hardcode payment parameters, and confirm before spending mainnet USDC. - Removed detailed local wallet setup; removed README.md (info now consolidated in SKILL.md). - Added explicit instructions for manual payment flow when not using `@x402/*` SDKs.

v0.1.6

Version 0.1.6 - Added a dedicated "Wallet Setup (Required)" section with explicit instructions for provisioning and funding a USDC wallet. - Clarified agent behavior: agents should check for wallet funding and stop with an error if no USDC wallet is available. - Updated agent rules to emphasize security best practices (never commit secrets, verify balances). - No changes to code or API usage; documentation only.

v0.1.5

- Simplified the skill to support direct HTTP calls to Maestro Bitcoin APIs using x402 USDC payments (Ethereum or Base) only. - Removed all local wrapper scripts and references to API key authentication. - Updated documentation to point agents directly to endpoint specs at https://docs.gomaestro.org/bitcoin. - Clarified workflow for handling 402 payment challenges and required headers. - Markedly reduced configuration complexity—wallet signing and HTTP requests are handled externally, not by this skill.

v0.1.4

- Added required and sensitive environment variable declarations (`required-env-vars`, `sensitive-env-vars`) to SKILL.md. - Introduced `MAESTRO_X402_SIGNER_PASSTHROUGH_VARS` to control environment exposure for x402 signer processes. - Updated documentation to clarify that x402 signer runs in a minimal environment by default, improving security. - Removed guidance for high-risk signer options and legacy env variables (`MAESTRO_X402_ALLOW_SHELL_SIGNER`, `MAESTRO_SHOW_PAYMENT_RESPONSE`), streamlining setup. - Expanded details and security advice for configuring authentication and external signers.

v0.1.3

- Added explicit security documentation including sensitive environment variables and guidance on signer risk. - Expanded SKILL.md with structured metadata for security, runtime behaviors, and requirements. - Documented new environment variables: `MAESTRO_X402_ALLOW_SHELL_SIGNER` and `MAESTRO_X402_SIGNER_TIMEOUT`. - Updated x402 authentication setup instructions and clarified logging/debugging controls. - Improved and clarified skill description to highlight support for both API key and x402 payment flows.

v0.1.2

**Changelog for maestro-skill v0.1.2** - Added x402 v2 payment flow documentation for all Maestro APIs (USDC on Ethereum or Base), including detailed step-by-step flow and environment variables. - Introduced explicit authentication modes (`auto`, `api-key`, `x402`) with environment variable configuration for flexible auth handling. - Enhanced documentation for wallet agent integration: explained signer command, supported environment variables, and payment challenge/response handling. - Updated usage instructions and configuration guidance to cover both API key and x402 payment flows. - Improved code and docs to support agents and tools without API keys via x402. - Added reference and API docs for new payments and authentication flows.

v0.1.1

Summary: Major overhaul with expanded API coverage, improved documentation, and enhanced usage instructions. - Expanded from basic block/transaction interactions to full support for 7 Maestro API services and over 100 endpoints, covering Bitcoin, metaprotocols (BRC20, Runes), price data, webhooks, and mempool features. - Rewrote and extended documentation with detailed command lists, configuration guides, API key and network selection instructions, and richer usage examples. - Added new documentation and example reference files (e.g., README.md, examples.md) to improve onboard experience. - Updated shell script usage to expose the broader command set and new capabilities. - Significant enhancement in descriptive detail for features and available operations.

v0.1.0

Initial release with Bitcoin network integration via Maestro API: - Enables querying block height, transaction details, and address UTXOs. - Supports broadcasting transactions to the Bitcoin network. - Usage provided through a shell script interface (`scripts/call_maestro.sh`). - Requires configuration of a Maestro API Key via environment variable.

Metadata

Slug maestro-skill

Version 0.2.4

License MIT-0

All-time Installs 1

Active Installs 1

Total Versions 13

Frequently Asked Questions

What is Maestro Api?

Query Maestro APIs over HTTP using the SIWX + JWT + x402 credit purchase flow. Resolve the exact endpoint from docs.gomaestro.org before requesting or paying. It is an AI Agent Skill for Claude Code / OpenClaw, with 1729 downloads so far.

How do I install Maestro Api?

Run "/install maestro-skill" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Maestro Api free?

Yes, Maestro Api is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Maestro Api support?

Maestro Api is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Maestro Api?

It is built and maintained by Varderes (@vardominator); the current version is v0.2.4.

More Skills