How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Hevn Inc mcp API

The mcp API from Hevn Inc — 14 operation(s) for mcp.

Hevn Inc mcp API is one of 31 APIs that Hevn Inc publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include MCP. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 16 operations across 14 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 0.1.2.

Requests are made against a single base URL, https://api.hevn.finance.

16 operations 14 paths 10 schemas 2 DELETE8 GET6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.2
Base URL
https://api.hevn.finance/api/v1
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

Hevn Inc mcp API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (HTTPBearer). An API key is passed in the header as x-api-key (ApiKeyAuth).

  • ApiKeyAuth — Alternative HEVN API key header. The CLI defaults to Authorization Bearer unless configured with HEVNAPIKEYHEADER=X-Api-Key.

Paths & Operations 16

Across 14 paths, the API surfaces 16 operations — 2 DELETE, 8 GET, 6 POST. Each is listed below with its method, path, parameters, and response codes.

mcp 16
POST
/api/v1/mcp/api_key
Create a new MCP API key
create_api_key_api_v1_mcp_api_key_post 4 params body → 200422
GET
/api/v1/mcp/api_key
List all MCP API keys
list_api_keys_api_v1_mcp_api_key_get 1 param → 200422
DELETE
/api/v1/mcp/api_key/{key_id}
Delete an MCP API key
delete_api_key_api_v1_mcp_api_key__key_id__delete 2 params → 200422
GET
/api/v1/mcp/get_balance
Get USDC balance on Base
get_mcp_balance_api_v1_mcp_get_balance_get 1 param → 200422
GET
/api/v1/mcp/resolve_address
Resolve smart wallet address by email
resolve_address_api_v1_mcp_resolve_address_get 2 params → 200422
POST
/api/v1/mcp/transfer
Transfer USDC through MCP using invoice/contact/quote context
transfer_api_v1_mcp_transfer_post 2 params body → 200422
POST
/api/v1/mcp/transfer_to_user
Transfer USDC to user via spend permission
transfer_to_user_api_v1_mcp_transfer_to_user_post 2 params body → 200422
GET
/api/v1/mcp/transfers
List MCP transfers for authenticated user
list_transfers_api_v1_mcp_transfers_get 4 params → 200422
POST
/api/v1/auth/mcp/api_key
Create a new MCP API key
create_api_key_package_alias_api_v1_auth_mcp_api_key_post 4 params body → 200422
GET
/api/v1/auth/mcp/api_key
List all MCP API keys
list_api_keys_package_alias_api_v1_auth_mcp_api_key_get 1 param → 200422
DELETE
/api/v1/auth/mcp/api_key/{key_id}
Delete an MCP API key
delete_api_key_package_alias_api_v1_auth_mcp_api_key__key_id__delete 2 params → 200422
GET
/api/v1/auth/mcp/get_balance
Get USDC balance on Base
get_mcp_balance_package_alias_api_v1_auth_mcp_get_balance_get 1 param → 200422
GET
/api/v1/auth/mcp/resolve_address
Resolve smart wallet address by email
resolve_address_package_alias_api_v1_auth_mcp_resolve_address_get 2 params → 200422
POST
/api/v1/auth/mcp/transfer
Transfer USDC through MCP using invoice/contact/quote context
transfer_package_alias_api_v1_auth_mcp_transfer_post 2 params body → 200422
POST
/api/v1/auth/mcp/transfer_to_user
Transfer USDC to user via spend permission
transfer_to_user_package_alias_api_v1_auth_mcp_transfer_to_user_post 2 params body → 200422
GET
/api/v1/auth/mcp/transfers
List MCP transfers for authenticated user
list_transfers_package_alias_api_v1_auth_mcp_transfers_get 4 params → 200422

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are ApiKeyListResponse (10 properties), app__schemas__routers__security__mcp__ApiKeyResponse (10 properties), McpTransactionResponse (6 properties), McpTransferContext (5 properties). Each schema is shown below with its type and property counts.

HTTPValidationError
object
1 property
BalanceResponse
object
4 properties 1 required
TransferResponse
object
3 properties
McpTransferContext
object
5 properties
ValidationError
object
3 properties 3 required
ApiKeyListResponse
object
10 properties 5 required
app__schemas__routers__security__mcp__ApiKeyCreateRequest
object
3 properties 1 required
McpTransactionResponse
object
6 properties 2 required
TransferRequest
object
3 properties 2 required
app__schemas__routers__security__mcp__ApiKeyResponse
object
10 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hevn-inc-mcp-api-openapi.yml Raw ↑

Other APIs Hevn Inc publishes across the network.

Hevn Inc 2FA API
Hevn Inc Activity API
Hevn Inc apps API
Hevn Inc apps-transfer API
Hevn Inc auth API
Hevn Inc B2B API
Hevn Inc Balance API
Hevn Inc Banks API
Hevn Inc Cards API
Hevn Inc Chat API
Hevn Inc contracts API
Hevn Inc Devices API
Where this information came from

This is an independent, third-party profile of Hevn Inc mcp API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.