run402-com

run402-com Vault API

The vault API from run402-com — 45 operation(s) for vault.

GitHub OpenAPI

Operations 50

GET /vaults/v1/repos List vault-backed repos for the signed-in principal #
POST /vaults/v1 Allocate the project's vault, or push-to-create it (owner / org member) #
GET /vaults/v1 Find a project's vault by project_id/repo address, or list every vault in an org #
GET /vaults/v1/{vault_id} Read the vault record #
POST /vaults/v1/{vault_id}/handoffs Mint a Handoff Key #
GET /vaults/v1/{vault_id}/handoffs List a vault's handoffs #
DELETE /vaults/v1/{vault_id}/handoffs/{handoff_id} Revoke a handoff #
POST /vaults/v1/handoffs/{handoff_id}/redeem Redeem a Handoff Key #
POST /vaults/v1/{vault_id}/invites Mint an Invite Key #
GET /vaults/v1/{vault_id}/invites List a vault's invites #
DELETE /vaults/v1/{vault_id}/invites/{invite_id} Revoke an invite #
POST /vaults/v1/invites/{invite_id}/redeem Redeem an Invite Key #
GET /vaults/v1/{vault_id}/state Read the composite pin-current state in one call #
POST /vaults/v1/{vault_id}/allocations/reclaim Reclaim a stalled allocation (owner-only) #
GET /vaults/v1/{vault_id}/heads List heads above your pin #
GET /vaults/v1/{vault_id}/heads/{generation} Read one head's exact stored bytes #
POST /vaults/v1/{vault_id}/head-reads Read many heads' exact stored bytes in one call #
GET /vaults/v1/{vault_id}/admissions/{generation} Read one admission record's exact stored bytes #
POST /vaults/v1/{vault_id}/object-reads Presign reads for stored objects #
POST /vaults/v1/{vault_id}/object-reads/bytes Read one stored object's exact bytes through the gateway #
GET /vaults/v1/{vault_id}/objects List every stored object in the vault #
GET /vaults/v1/{vault_id}/envelope-recipients List the fingerprints currently covered by this vault's key envelopes, plus the… #
POST /vaults/v1/{vault_id}/upload-sessions Open an upload session, or upload small objects inline in one call #
GET /vaults/v1/{vault_id}/upload-sessions/{upload_session_id} Read an upload session (redacted) #
DELETE /vaults/v1/{vault_id}/upload-sessions/{upload_session_id} Abort an upload session (redact) #
POST /vaults/v1/{vault_id}/upload-sessions/{upload_session_id}/finalize Finalize an upload session #
POST /vaults/v1/{vault_id}/maintenance-leases Acquire the maintenance lease (owner-only) #
POST /vaults/v1/{vault_id}/maintenance-leases/{maintenance_lease_id}/heartbeat Renew the maintenance lease #
DELETE /vaults/v1/{vault_id}/maintenance-leases/{maintenance_lease_id} Release the maintenance lease #
POST /vaults/v1/{vault_id}/compaction-grant Open a bounded compaction headroom grant #
DELETE /vaults/v1/{vault_id}/compaction-grant Close the compaction headroom grant (idempotent) #
POST /vaults/v1/{vault_id}/repair-attempts Open the repair resource lane (owner + step-up) #
PATCH /vaults/v1/{vault_id}/policy Set the project's vault policy (owner + step-up) #
POST /vaults/v1/{vault_id}/override-completions Close an unvaulted-deploy advisory #
POST /vaults/v1/{vault_id}/rotation-attempts Create a rotation_attempt_descriptor (writer) #
POST /vaults/v1/{vault_id}/recipients/{principal_id}/confirm First-seen pin confirmation (owner + step-up) #
GET /vaults/v1/{vault_id}/recipients/{principal_id} Recipient pin status (owner + step-up) #
POST /vaults/v1/{vault_id}/recipients/{principal_id}/proof-of-open Submit a recipient proof-of-open (rev 44 D210) #
POST /vaults/v1/{vault_id}/recipients/{principal_id}/repin Re-pin ceremony (owner + step-up) #
POST /vaults/v1/{vault_id}/recipients/{principal_id}/key-revocation Declare a recipient key revoked (owner + step-up) #
POST /vaults/v1/{vault_id}/epoch-secret-exposure Declare this vault's epoch secret exposed (owner + step-up) #
POST /vaults/v1/{vault_id}/writers/retire-previous-owner Retire a previous owner's vault writers after a project transfer (owner +… #
POST /vaults/v1/{vault_id}/writer-authority/declare-unavailable Declare the writer signing key unavailable (owner + step-up) #
POST /vaults/v1/{vault_id}/admissions Admit a signed head (the push) #
POST /vaults/v1/{vault_id}/retention-cutoffs Mint a retention cutoff ticket #
POST /vaults/v1/{vault_id}/activation-tokens Exchange a capture receipt for an activation token #
POST /vaults/v1/{vault_id}/maintenance/open Open a maintenance cycle (owner) #
POST /vaults/v1/{vault_id}/maintenance/abort Abort a maintenance cycle before its first checkpoint (owner) #
POST /vaults/v1/{vault_id}/prune-intents Submit a prune intent (owner) #
GET /vaults/v1/{vault_id}/prune-intents/{prune_intent_object_id} Read a prune intent (owner) #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/run402-com/openapi/run402-com-vault-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://artifacts.apis.io/run402-com/json-schema/run402-com-project-transfer-preview-schema.json
📊
JSONSchema
https://artifacts.apis.io/run402-com/json-schema/run402-com-deploy-plan-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/run402-com/json-schema/run402-com-stable-host-resolve-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/run402-com/json-schema/run402-com-release-inventory-schema.json
📊
JSONSchema
https://artifacts.apis.io/run402-com/json-schema/run402-com-mailbox-schema.json
📊
JSONSchema
https://artifacts.apis.io/run402-com/json-schema/run402-com-project-event-feed-page-schema.json

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/run402-com:run402-com-vault-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

run402-com-vault-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Run402 Vault API
  version: 2.0.0
  description: 'Full-stack infrastructure for AI agents. Postgres, REST API, auth, file storage, static site hosting, serverless functions. Tier payments and image generation use the shared payment engine: x402 (USDC on Base), MPP on Tempo (pathUSD), and the draft-pinned MPP Lightning charge profile (sats, Bitcoin mainnet) for authenticated tier purchases and image generation.'
  contact:
    name: Run402
    url: https://run402.com
  guidance: 'Run402 is a pay-per-use backend for AI agents: Postgres databases, static hosting, serverless functions, and image generation. The shared payment engine supports x402 (USDC on Base), MPP on Tempo (pathUSD), and the exact Run402 MPP Lightning charge profile on Bitcoin mainnet (sats).


    ## Quick start

    1. Install the CLI: npm install -g run402@latest

    2. Create an allowance: run402 init

    3. Set the prototype tier (FREE, testnet USDC): run402 tier set prototype

    4. Provision a project: run402 projects provision --name "my-app"

    5. Deploy: run402 deploy --manifest app.json


    ## Payment model

    - Tiers (prototype $0.10 testnet, hobby $5, team $20; hobby and team are 30-day prepaid leases) unlock all platform features.

    - Image generation is $0.03 per call (x402, MPP on Tempo, or MPP Lightning micropayment).

    - Auth-only endpoints (projects, deploys, messages) require SIWX wallet identity but no payment.


    ## Auth

    - x402 endpoints: include a payment header (handled automatically by the CLI or x402 client libraries).

    - Explicit MPP Lightning tier requests require the exact Run402 profile, ordered Accept-Payment preferences, one principal credential, a stable Idempotency-Key, and buyer-side USD/native/fee limits.

    - SIWX endpoints: sign a CAIP-122 message with your wallet.

    - REST API: use the project''s anon_key or service_key as the apikey header.


    ## Client metadata

    - Recent Node SDK/CLI clients may send Run402-Client: surface="cli", version="3.7.14", sdk="3.7.14". It is advisory, bounded, never used for auth/billing/trust, and not browser-CORS-enabled yet.


    ## Docs

    - Full CLI docs: https://run402.com/llms-cli.txt

    - API docs: https://run402.com/llms.txt'
servers:
- url: https://api.run402.com
  description: Production
tags:


# --- truncated at 32 KB (233 KB total) ---
# Full source: https://artifacts.apis.io/run402-com/openapi/run402-com-vault-api-openapi.yml