Skip to main content

hanzo-tools-api

Generic API tools for Hanzo MCP:

  • api: OpenAPI-first generic REST tool
  • hanzo: Unified Hanzo platform router (auth, billing, commerce, iam, ingress, kms, mpc, paas, team, api)

Features

  • Credential Management: Securely store and manage API keys with env var fallback
  • OpenAPI Support: Parse OpenAPI 3.x specs to discover and call operations
  • Auto-Detection: Automatically detects credentials from environment variables
  • Multi-Provider: Built-in support for 30+ cloud providers
  • Raw Requests: Make raw HTTP requests when you need more control

Installation

pip install hanzo-tools-api

Quick Start

Set your API keys as environment variables:

export CLOUDFLARE_API_TOKEN=your-token
export GITHUB_TOKEN=ghp_xxx
export STRIPE_API_KEY=sk_xxx

The tool automatically detects these when you make calls.

Using the Tool

from hanzo_tools.api import APITool

tool = APITool()

# List available providers and their status
await tool.call(ctx, action="list")

# Configure a provider manually
await tool.call(ctx, 
    action="config",
    provider="cloudflare",
    api_key="your-key"
)

# Load OpenAPI spec for a provider
await tool.call(ctx, action="spec", provider="cloudflare")

# List available operations
await tool.call(ctx, action="ops", provider="cloudflare", search="zones")

# Call an operation
await tool.call(ctx,
    action="call",
    provider="cloudflare",
    operation="listZones"
)

# Make a raw request
await tool.call(ctx,
    action="raw",
    provider="github",
    method="GET",
    path="/user/repos"
)

Unified Hanzo Platform Tool

from hanzo_tools.api import HanzoTool

tool = HanzoTool()

# Discover available services
await tool.call(ctx, service="services")

# Route to service tools through one MCP surface
await tool.call(ctx, service="auth", action="status")
await tool.call(ctx, service="commerce", action="orders")
await tool.call(
    ctx,
    service="iam",
    action="enforce",
    args='{"owner":"hanzo","model":"rbac","resource":"/api/users","permission_action":"read"}',
)

MCP Tool Usage

When registered with hanzo-mcp, use like:

api                                    # List all providers
api --action config --provider github --api_key ghp_xxx
api --action ops --provider cloudflare --search zones
api --action call --provider cloudflare --operation listZones
api --action raw --provider github --method GET --path /user/repos

Supported Providers

Built-in configurations for:

Provider Env Variables
Cloudflare CLOUDFLARE_API_TOKEN, CF_API_TOKEN
GitHub GITHUB_TOKEN, GH_TOKEN
Stripe STRIPE_API_KEY
OpenAI OPENAI_API_KEY
Anthropic ANTHROPIC_API_KEY
Vercel VERCEL_TOKEN
DigitalOcean DIGITALOCEAN_TOKEN, DO_TOKEN
Fly.io FLY_API_TOKEN
Supabase SUPABASE_API_KEY
AWS AWS_ACCESS_KEY_ID
GCP GOOGLE_API_KEY
Azure AZURE_API_KEY
Slack SLACK_TOKEN
Discord DISCORD_TOKEN
... and more

API Reference

Actions

  • list: Show all providers and their configuration status
  • config: Set credentials for a provider
  • delete: Remove credentials for a provider
  • spec: Load/refresh OpenAPI spec for a provider
  • ops: List available operations for a provider
  • call: Call an API operation by operation ID
  • raw: Make a raw HTTP request to any endpoint

Parameters

Parameter Type Description
action str Action to perform (default: "list")
provider str Provider name (e.g., "cloudflare")
api_key str API key for config action
api_secret str API secret (if needed)
account_id str Account/org ID
base_url str Override base URL
spec_url str URL to OpenAPI spec
operation str Operation ID for call action
params str JSON parameters
body str JSON request body
method str HTTP method for raw action
path str URL path for raw action
search str Search filter for ops action
tag str Tag filter for ops action

Credential Storage

Credentials are stored in ~/.hanzo/api/credentials.json with basic obfuscation. For production use, consider using system keyring or a secrets manager.

OpenAPI specs are cached in ~/.hanzo/api/specs/.

Adding Custom Providers

You can add any provider by providing a base URL and API key:

from hanzo_tools.api import get_credential_manager

cred_manager = get_credential_manager()
cred_manager.set_credential(
    provider="custom-api",
    api_key="your-key",
    base_url="https://api.custom.com/v1"
)

Then load a spec:

from hanzo_tools.api import get_client

client = await get_client(
    "custom-api",
    spec_url="https://api.custom.com/openapi.json"
)

Security Notes

  • API keys are stored with basic base64 obfuscation (not encryption)
  • Credentials file has restrictive permissions (0600)
  • Environment variables are preferred for sensitive credentials
  • Never commit credentials to version control

License

MIT

Metadata

Release files for hanzo-tools-api 0.3.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for hanzo-tools-api 0.3.3
File Size Uploaded Provenance Actions
hanzo_tools_api-0.3.3.tar.gz 229.3 kB Without provenance Details for hanzo_tools_api-0.3.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for hanzo-tools-api 0.3.3
File Interpreter ABI Platform Actions
hanzo_tools_api-0.3.3-py3-none-any.whl Python 3 none any Details for hanzo_tools_api-0.3.3-py3-none-any.whl

Total release size: 382.5 kB

Release files / hanzo_tools_api-0.3.3.tar.gz

Download URL hanzo_tools_api-0.3.3.tar.gz
Size 229.3 kB
Tags Source
SHA-256 checksum
How to use checksums
f5aa5f058889d73fc88a7017f962e12f1ebfd6160cb77ab7a90146e480da51a5
BLAKE2b-256 checksum
How to use checksums
c20ce3a373b57e7ec9bb663522112731ea9245cd9bceae6df89532de4664c66e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.9

Release files / hanzo_tools_api-0.3.3-py3-none-any.whl

Download URL hanzo_tools_api-0.3.3-py3-none-any.whl
Size 153.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ab00cc4a7436fd9bfcf348ec38179bac7c415fc9bbaba95a0c0662e037b23779
BLAKE2b-256 checksum
How to use checksums
34ac21c57cc6f16d7d1280392c99456f75f65b00feb13ce9ab44f471b827d3ab
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.9

Security for hanzo-tools-api 0.3.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page