Add credits to a Locus Platform workspace via MPP-settled payment
What it does
This endpoint is part of the Locus Platform (Build With Locus), a containerized deployment platform that offers Postgres, Redis, custom domains, and REST-API-driven service management with pay-per-use credit billing. The specific endpoint at `/v1/billing/mpp-top-up` is intended to let callers top up workspace credits using the MPP (Micropayment Protocol) payment flow.
During probing, the endpoint returned HTTP 404 on both HEAD and GET requests rather than the expected 402 MPP challenge. This likely means the endpoint is either POST-only (common for billing/top-up actions) or is not currently active. The root origin at `mpp.buildwithlocus.com` does respond with a 200 and identifies itself as "Locus Platform API v0.1.0", confirming the server is running. However, no OpenAPI spec, documentation pages, or pricing information were found — all auxiliary routes (`/docs`, `/api`, `/pricing`, `/README`) return 404.
Because no 402 challenge was captured, the payment method, token, network, and per-call price are unknown. The endpoint may require a POST request to trigger the MPP challenge, but this cannot be confirmed from the available probe data. Users interested in this endpoint should contact the Locus Platform team or attempt a POST request to determine current availability and pricing.
Capabilities
Use cases
- —Programmatically adding credits to a Locus Platform workspace for container deployments
- —AI agents autonomously purchasing compute credits to deploy services
- —Automating billing top-ups as part of a CI/CD or orchestration pipeline
Fit
Best for
- —Developers using the Locus Platform who want automated credit management
- —AI agents that need to provision cloud resources and pay per use
- —Programmatic billing integrations with MPP-compatible wallets
Not for
- —Users looking for a general-purpose cloud provider API — this is a single billing endpoint
- —Anyone needing detailed documentation or guaranteed uptime — the endpoint did not return a 402 challenge during probing
Quick start
# Attempt to trigger the MPP challenge (likely requires POST)
curl -X POST https://mpp.buildwithlocus.com/v1/billing/mpp-top-up \
-H "Content-Type: application/json" \
-d '{"workspace_id": "your-workspace-id"}'Endpoint
Quality
The endpoint did not return a 402 MPP challenge on HEAD or GET, so payment parameters (token, network, price) are unknown. No documentation, OpenAPI spec, or pricing info was found. The server is running (root returns 200) but the specific endpoint may only respond to POST or may not be active. Almost all listing details are inferred from the existing Bazaar description.
Warnings
- —Endpoint returned 404 on HEAD and GET — no MPP 402 challenge captured; it may require POST or may not be live
- —No OpenAPI spec or documentation found at any probed path
- —Pricing, payment token, and network are completely unknown
- —Platform API is version 0.1.0 — early stage, may change without notice
Citations
- —Root origin responds with 200 and identifies as Locus Platform API v0.1.0https://mpp.buildwithlocus.com
- —Endpoint returned 404 on HEAD and GET probeshttps://mpp.buildwithlocus.com/v1/billing/mpp-top-up
- —Locus Platform offers containerized services, Postgres, Redis, and custom domains via REST API with pay-per-use credit billinghttps://mpp.buildwithlocus.com/v1/billing/mpp-top-up