Build finance workflows with explicit controls.

Start

Canonical endpoint

Base URL  https://api.allfullness.com/api/agent
OpenAPI   /openapi.json

Do not infer production availability from an endpoint appearing in this documentation. Check the capability registry and your tenant's negotiated release policy.

OAuth

Scoped access and explicit consent

Authorization server metadata  /.well-known/oauth-authorization-server
Protected resource metadata    /.well-known/oauth-protected-resource

Use OAuth 2.0 authorization code with PKCE where applicable. Ask only for required scopes, preserve tenant context, support revocation, and never treat a token as approval for a consequential action.

Agent Action API

Execute, wait, and inspect

POST /external/v1/actions/{tool}/execute
GET  /external/v1/actions/{action_id}

• Send an idempotency key for non-read actions.
• Handle waiting_approval as a durable state, not an error.
• Follow returned approval and evidence links.
• A client or external agent cannot approve its own request.
• Denied, unavailable, or unreleased capabilities fail closed.

Agent protocols

MCP and agent-to-agent

MCP endpoint    /external/mcp
A2A endpoint    /external/a2a
Agent Card      /.well-known/agent-card.json

Tool discovery does not bypass capability, scope, tenant, policy, or approval enforcement. The Agent Card describes what may be requested; runtime policy determines what may execute.

SDKs

TypeScript and Python

TypeScript  @fullness/agent-api
Python      fullness-agent (repository SDK)

SDKs preserve the API's action IDs, idempotency, approval states, errors, and evidence links. They do not convert beta capabilities into generally available features.

Webhooks

Verify before processing

Webhook management  /v1/external/webhooks

Verify the signature headers against the raw request body, reject stale or replayed deliveries, store delivery IDs idempotently, and rotate secrets through the supported management flow.

Operational contract

Errors, limits, and tenant boundaries

Clients must handle authentication, authorization, consent, policy, approval, release-gate, validation, conflict, throttling, and transient-service failures separately. Published numeric rate limits are plan- and tenant-specific; use response metadata and negotiated policy rather than hard-coded assumptions.

Sandbox

Research is not money movement

Sandbox payment tooling is for controlled research and integration testing. It is not authorization for production money movement, custody, settlement, or regulated payment activity.

Changelog

Public contract changes

2026-08-31 — Published the canonical controlled-beta guide for OpenAPI, OAuth, Agent Action API, SDKs, webhooks, MCP, A2A, approval states, and release boundaries.

Machine-readable changelog · Developer-docs manifest