Key Differences from the Standard API

Simplified Authentication

AI Agents do not need to generate or manage complex access tokens.

Instead, an agent can authenticate with any wallet address by using personalSign. Requests should include the following headers:

Authorization: PersonalSign {sign}.{timestamp}
X-Address: {evmAddress}

Where:

{sign} is the signature generated via personalSign
{timestamp} is the signing timestamp
{evmAddress} is the wallet address used for signing

This authentication model is designed to better fit agent-based systems, where lightweight, wallet-based access is often more practical than traditional token issuance flows.

Usage Package–Based Billing

This version does not require credit card subscriptions.

Instead of subscribing through a conventional billing model, users can purchase the required usage package and consume the service accordingly. This makes the API easier to adopt in automated and programmatic environments, especially for agent workflows with variable or prepaid usage patterns.

x402 Payment Support

Payments are supported through the x402 protocol.

This provides a faster and more convenient payment flow for AI Agent scenarios, especially where machine-to-service payment, automation, and low-friction access are important. It also makes the service easier to integrate into crypto-native and agent-native systems.

Why This Version Exists

Traditional API access models are usually designed for human-operated applications. AI Agents have different requirements:

simpler authentication flows
programmatic access control
flexible usage-based consumption
automated payment support

This agent-optimized Security API is designed to meet those requirements directly, making it easier to integrate security capabilities into autonomous agents, AI applications, wallets, and onchain workflows.