BNZ Platform API · v2.4.1

Build on digital asset infrastructure

Use one API for portfolio data, order workflows and operational automation. The platform supports OAuth 2.0, scoped service credentials and MCP-compatible integrations.

Base URL · https://brunomenozzi.comRegion · SA-EAST-1JSON over HTTPS

Authentication

Interactive applications use the authorization code flow. Server workloads should use a scoped service credential created in the Console.

Keep credentials server-side. Never embed a service token in client JavaScript, logs or public repositories. Production access is audited and subject to tenant policy.

Authorization header

Authorization: Bearer $BNZ_ACCESS_TOKEN
Accept: application/json

Quickstart

Read the platform configuration used by an integration, then follow the endpoint metadata returned for the active tenant.

Configuration snapshot

curl -sS https://brunomenozzi.com/api/v2/internal/config \
  -H "Accept: application/json"

The response includes a request ID, regional service metadata and integration links. Treat any credential-shaped field as sensitive.

Core endpoints

These endpoints are available to platform and partner integrations. Required scopes are shown on each operation.

GET/api/v2/internal/configinfra:read

Returns the regional service configuration and the next integration action for the active tenant.

POST/oauth/tokenpublic

Exchanges an authorization code for an access token and OpenID Connect identity token.

POST/api/v2/mcp/streammcp:tools

Streamable HTTP transport for approved automation clients and operator tools.

Automation

BNZ publishes machine-readable discovery documents for clients that support MCP and agent cards. Use the same OAuth or service credential scopes as the REST API.

Automation clients should preserve the bnz_sid session cookie while following multi-step operational workflows.

Machine-readable resources

OpenAPI JSONREST operations and OAuth schemes OpenAPI YAMLPortable specification for tooling MCP discoveryTransport and capability metadata Agent cardAutomation client capabilities LLM referenceCompact integration context Security policyReporting and contact information