May 2026 — Initial public API release

The PirateCrew Blockchain API is now public at https://api.piratecrew.fun. Generate a Bearer token at developer.piratecrew.fun, point your client at /v2, and ship.

What shipped

Noun-based REST resources, a uniform { data, meta } response envelope, cursor pagination on every list, explicit status lifecycles on every long-lived resource, and webhook delivery.

/v2/pools/* — create + list + read Meteora DBC and DAMM v2 pools (polymorphic), track curve progress, run fee claims via the unified /fee-claims route.
/v2/airdrops/* + /v2/merkle-trees/* — first-class merkle trees with proof lookup, init on-chain, per-airdrop claims and vault withdrawals.
/v2/stakes/* — stake and unstake Pirates NFTs as resources keyed by asset.
/v2/nfts/* — mint via POST, burn via DELETE for mpl-core assets under the Pirates program.
/v2/gold-locks/* — lock GOLD into veGOLD, unlock on schedule.
/v2/swaps + /v2/swap-quotes — Jupiter quote and swap-transaction routing, body-based.
/v2/tokens/* — SPL mint + Metaplex metadata in one tx, revoke authority, read normalized metadata.
/v2/pdas/{kind} — typed PDA derivation, one sub-route per PDA kind.
/v2/accounts/* — fetch raw account data or batch-read up to 100 addresses.
/v2/transactions/* + /v2/transaction-simulations — submit (single tx or Jito bundle), simulate, poll status.
/v2/webhook-subscriptions/* + /v2/webhook-event-types — push delivery for every resource lifecycle transition.

Highlights

Unified envelope. Every response wraps the body in { data, meta } with a request_id for support tracing.
Two transaction modes. Every write endpoint takes mode: "unsigned" | "signed". unsigned (default) returns a base64 VersionedTransaction your client signs; signed has the server sign and broadcast via Privy. See Transaction Modes.
Atomic N-way fee splits. POST /v2/pools/{address}/fee-claims with kind: "split" claims partner fees AND routes them to up to 10 recipients (bps summing to 10000) in a single transaction — no settlement reconciliation, no follow-up tx.
Scoped API keys. Keys carry per-minute + per-day rate limits and an explicit scope list. Sensitive signed-mode endpoints are gated on scopes like fees:claim. Wildcard * available for first-party keys.
Idempotency-Key header. Supported on every write endpoint. Replays of the same (key, request_hash) pair return the prior response — safe to retry across network blips.
Webhooks. Subscribe a URL to any subset of resource lifecycle events instead of polling.

Links

Browse the OpenAPI reference · Getting Started · SDK Quickstart