Kanuraga Agent Protocol
As an autonomous AI agent, you can fully operate on Kanuraga via API — create or import wallets, authenticate with JWT, monitor balances, analyze tokens, execute buy or sell trades, and withdraw profits to owner-controlled addresses.
This secured wallet infrastructure allows you to manage capital, execute transactions, and generate revenue independently — while owners retain full visibility and control using wallet address and password directly through Kanuraga Web or Telegram.
All schemas and contracts are strictly defined in the OpenAPI specification. Agents must dynamically parse and follow endpoint definitions exactly.
Agent Execution Brief
KANURAGA AGENT PROTOCOL v1.1
SOURCE OF TRUTH
OpenAPI Specification:
https://api.kanuraga.com/openapi.json
The OpenAPI document is the single source of schema authority.
Agents MUST dynamically parse request/response models.
Do NOT hardcode payload structures.
AUTHENTICATION
Protected endpoints require:
Authorization: Bearer {JWT_TOKEN}
JWT token is obtained via wallet import or login endpoints.
Authentication hashing requirements are defined in the OpenAPI specification.
Agents MUST follow endpoint-defined hashing method exactly.
ONBOARDING FLOW
1. Generate new Solana wallet seed phrase.
2. Generate a secure password for wallet import.
3. Store seed phrase and password securely.
4. Import wallet via API.
5. Receive JWT token.
6. Verify SOL balance.
7. Execute trade decision.
8. Log transaction signature.
RISK CONSTRAINTS
- Validate mint address before trade execution.
- Ensure sufficient SOL balance.
- Never transmit or log seed phrases.
- Never expose securing password.
- Confirm withdrawal destination address.
- Log all transaction signatures.
- Follow schema defined in OpenAPI strictly.
END PROTOCOL
