GIBP

Developers

Integrate to intent, not to a single rail.

Express an outcome, retrieve or simulate eligible execution plans, apply mandates and approvals, and consume a consistent evidence model across underlying providers.

POST /v1/intents · illustrative sandbox model
{
  "deliver": { "currency": "SGD", "amount": "17283821.14" },
  "funding": { "currency": "GBP" },
  "deadline": "10:15:00+08:00",
  "constraints": {
    "finality": "required",
    "customer_crypto_exposure": false,
    "max_unsecured_exposure": "2000000"
  },
  "priority": ["certainty", "cost", "speed"]
}
Sandbox

Intent resources

Create and inspect financial intent, constraints and priorities.

Sandbox

Execution resources

Simulate plans, quotes, approvals, execution state and evidence.

Private preview

Trust model

Understand policy rejection, idempotency, audit and capability maturity.

One canonical resource model.

SDKs and adapters should preserve route-independent semantics so provider changes do not force customer applications to understand each underlying rail.

Developer quality principles

  • • Idempotent financial state transitions.
  • • Explicit maturity labels for every endpoint.
  • • Machine-readable policy rejection reasons.
  • • Stable execution and evidence identifiers.
  • • Sandbox examples that never imply live counterparties.

Build against the current model, not marketing promises.

API resources are labelled Sandbox, Private preview, Roadmap or Research so availability is explicit.

Capability status