Overview
The Giza API provides direct HTTP access to all agent services. This is the underlying API that powers the SDK.For most use cases, we recommend using the TypeScript SDK which provides type safety, automatic authentication, and better error handling. Use the HTTP API directly when:
- Building in a language without SDK support
- Needing lower-level control
- Integrating with existing HTTP infrastructure
Base URL
API Groups
Agents
Core agent operations: activation, monitoring, withdrawals
Protocols
DeFi protocol information and availability
Optimizer
Capital allocation optimization
Statistics
Platform-wide statistics and TVL
Rewards
Reward staking status and history
Support
Supported chains and tokens
Common Parameters
Chain ID
Most endpoints require achain_id path parameter:
| Chain | ID |
|---|---|
| Base | 8453 |
| Ethereum | 1 |
| Arbitrum | 42161 |
| Polygon | 137 |
| Base Sepolia | 84532 |
| Sepolia | 11155111 |
Wallet Address
Wallet addresses must be valid Ethereum addresses:- Start with
0x - 42 characters total (0x + 40 hex characters)
- Case-insensitive
Response Format
All successful responses return JSON with the following structure:HTTP Status Codes
| Code | Description |
|---|---|
200 | Success |
201 | Created |
204 | No Content (success with no response body) |
400 | Bad Request - Invalid parameters |
401 | Unauthorized - Invalid API key |
403 | Forbidden - Access denied |
404 | Not Found - Resource doesn’t exist |
422 | Validation Error - Invalid input |
500 | Internal Server Error |
503 | Service Unavailable |
Rate Limits
API requests are rate-limited per partner. If you exceed limits, you’ll receive a429 Too Many Requests response.
OpenAPI Specification
The complete API specification is available in OpenAPI 3.1 format:- Generate client libraries
- Import into Postman
- Validate requests
Interactive API Explorer
Swagger UI
Try API endpoints directly in the interactive Swagger documentation