Access Control

Check your token balance before making API requests.

Convenience Endpoint

This endpoint is for checking your balance only. It does not grant API access.

Actual access control on protected endpoints is enforced server-side with fixed parameters (token mint, minimum balance, RPC) that cannot be manipulated.

Endpoint

POST/v1/access/check

Request

Headers

Authorization: Bearer YOUR_API_KEY
X-Wallet-Address: YOUR_WALLET_ADDRESS
Content-Type: application/json

Body

{
  "owner": "YOUR_WALLET_ADDRESS"
}

Schema

Field	Type	Required	Description
owner	string	Yes	Wallet address to check

Server-Side Verification

The token mint, minimum balance, and RPC are configured server-side and used automatically. You don't need to specify them.

Response

Access Granted

{
  "allowed": true,
  "reason": "Sufficient balance",
  "balance": 125000.0
}

Access Denied

{
  "allowed": false,
  "reason": "Insufficient balance. Required: 50000, Found: 25000",
  "balance": 25000.0
}

Examples

cURL

curl -X POST https://api.actobotics.net/v1/access/check \
  -H "Authorization: Bearer acto_abc123..." \
  -H "X-Wallet-Address: 5K8vK..." \
  -H "Content-Type: application/json" \
  -d '{
    "owner": "5K8vK...",
    "mint": "ACTO_TOKEN_MINT",
    "minimum": 50000
  }'

Python SDK

from acto.client import ACTOClient

client = ACTOClient(api_key="...", wallet_address="...")

result = client.check_access(
    owner="5K8vK...",
    mint="ACTO_TOKEN_MINT",
    minimum=50000
)

if result.allowed:
    print(f"✅ Access granted. Balance: {result.balance}")
else:
    print(f"❌ Access denied: {result.reason}")

CLI

# Simple (uses configured ACTO token)
acto access check --owner 5K8vK...

# With explicit parameters
acto access check \
  --owner 5K8vK... \
  --mint ACTO_TOKEN_MINT \
  --minimum 50000

Use Cases

• Pre-flight access check
• Balance monitoring
• Multi-wallet validation