Python SDK
Client primitives for integrating with the control plane. SDK access does not itself stop an unguarded upstream call.
Integrate at the consequential call. Keep authority, business inputs and the effective request aligned.
Client primitives for integrating with the control plane. SDK access does not itself stop an unguarded upstream call.
Typed client integration for application and workflow code. Keep privileged credentials server-side.
Configured refund and deployment operations with workload-bound ingress and strict business inputs.
Reference integration for tool-mediated requests. Do not assume the mapped HTTP protections apply unchanged to MCP.
Mapped mode exposes POST /v1/operations/{operation_id}/enforce and POST /v1/operations/{operation_id}/release. The caller does not supply its own tenant, actor, upstream URL or independent business body.
Use exactly one workload bearer credential over TLS. Release sends the same input object and idempotency key plus the ticket. Identity, operation scope, expiry, binding and single-use checks remain mandatory.
POST /v1/operations/refund/enforce
Authorization: Bearer <WORKLOAD_TOKEN>
Content-Type: application/json
{
"idempotency_key": "refund-order-001",
"inputs": {
"payment_id": "pay-1",
"amount_minor": 4500,
"currency": "GBP"
}
}Contract example · provision your own reviewed endpoint and credentials.
Unknown fields, duplicate JSON properties, invalid types and invocations over 16 KiB are rejected in the mapped interface.
The mapping constructs both the authorization parameters and the upstream request from one set of business values.
Configured high-entropy opaque credentials are bound to a principal, tenant, operations and expiry. This is not an OIDC issuer or mTLS service.
Workload credentials and the gate’s control-plane credential are distinct. Do not expose either in browser bundles.
Provision reviewed mappings, trusted HTTPS endpoints, least-privilege credentials and signing-key material through an appropriate secret-management process.
The production HTTP gate refuses legacy sandbox mode. Network policy must restrict egress and prevent direct upstream bypass. Real TLS, DNS, private-CA and topology behavior require environment-specific validation.
Define the actions, limits and approval process your team needs.
Let’s discuss your pilot