Fiber Payment Gateway for Agent Backends
Spindle provides authentication, scope enforcement, and audit reconciliation for automated payments on CKB. A narrow control layer built for Fiber testnet operations.
A gateway is a control boundary.
Implicit vs. Explicit
Agent backends should not talk to Fiber directly. Spindle makes every automated intent explicit and auditable before execution.
Narrow Gateway
We are not a proof platform. We are a policy-enforcement gateway for Fiber testnet. Authority through constraint, not scope creep.
Real Reconciliation
The gateway reconciles local state with Fiber RPC reality, recovering stale processing records into final technical outcomes.
Request Lifecycle
API key validation and route-level scope enforcement.
Tenant-scoped isolation for all payment records.
Spend limits and recipient allowlist verification.
Fiber RPC calls against owned testnet nodes.
Honest retry handling for settled or in-flight payments.
Record persistence and audit registry query access.
Concrete Capabilities
Spindle is judged on concrete gateway behavior. We enforce technical boundaries between agent backends and Fiber RPC nodes.
| CAPABILITY_ID | CORE_LOGIC | CLASS |
|---|---|---|
| AUTH_SCOPE | API Key + Route Scoped Permissions | L1_GATEWAY |
| FIBER_SYNC | Fiber Testnet Invoice Reconciliation | CORE_PAYMENT |
| POLICY_GATE | Pre-execution spending limit enforcement | CONTROL_LAYER |
| AUDIT_RECAP | Full lifecycle audit row persistence | COMPLIANCE |
| IDEMPOTENT_RETRY | Stateful duplicate execution blocking | SYSTEM_INTEGRITY |
Technical Integration
{
"amount": "50",
"assetSymbol": "USDT",
"description": "Agent payout"
}{
"invoice": "fibt1..."
}Review the implementation.
The documentation and seeded scenarios provide the definitive API shape and request flow of the current Spindle Gateway.