Platform Reference
Pricing, fees, credentials, security, and technical limits
- Advanced Technical DetailsCircuit breaker, precision, rate limits, storage limits, and error handling details
- Credentials System Deep DiveHow credential resolution works — three-tier hierarchy, Secure Vault, BYOK, and API cost tracking.
- Known LimitationsWhat's not ready yet — transparency about current platform limitations
- Pricing & Fees ReferenceComplete fee schedule for indie.money — execution fee, purchase fee, withdrawal fee, and publishing fee.
- Service Composition (Workflow-to-Workflow Calls)How one workflow can invoke another via Execute Workflow node; the callee is billed to its own owner's budget (owner-pays)
- Technical Architecture OverviewHow indie.money works — workflow ownership, wallets, discovery, and the execution flow
- File Handling & Size LimitsHow indie.money handles files, binary data, and what size limits apply
- Bring Your Own Wallet (Production Setup)Use indie.money with an external wallet for production — payments signed locally by x402-proxy, private keys never leave your machine
- Which MCP Endpoint Should I Use?Code Mode vs local signer vs bring-your-own-signer — pick the right indie.money MCP connection.
- indie.money MCP Tool CatalogEvery indie.money MCP tool exposed through Code Mode — 89 namespaced methods across public, buyer, maker, and credentials.
- Call a Paid MCP Server from Your Code (x402)Run indie.money workflows from your own code and pay per call with the open x402 standard — bring your own signer, your key never leaves your machine.
- Call Workflows from the Browser (SIWX + x402)Call a workflow's webhook straight from a browser dApp — the user's wallet signs identity and payment, keys never leave the wallet.
- Send Traces to Your Own CollectorPoint indie.money at an OTLP collector and every run arrives as a trace, with one child span per node.