REST

API Documentation

REST reference — search tools, call tools, handle errors.

Quick Start

Uno has two endpoints. That's it.

1. Search Tools

GET/v1/tools
http
GET /v1/tools?q=weather&limit=5
Authorization: Bearer <API_KEY>

Returns tools with input_schema (JSON Schema) so you know exactly what arguments to pass.

2. Call a Tool

POST/v1/call
http
POST /v1/call
Authorization: Bearer <API_KEY>
Content-Type: application/json

{"tool": "amap-maps.weather", "arguments": {"city": "北京"}}
JSON

Response Format

json
{
  "data": {"temperature": "22C", "weather": "晴"},
  "error": null,
  "meta": {"latency_ms": 234, "credits_used": 1.0}
}

Authentication

All requests need a Bearer token (API Key). Get one from the Dashboard.

For CLI Agents (Device Code Flow)

shell
# 1. Request device code
curl -s -X POST https://agentools.uno/oauth/device/code \
  -d '{"client_id":"my-agent"}'

# 2. User authorizes, then poll for token
curl -s -X POST https://agentools.uno/oauth/token \
  -d '{"device_code":"DEVICE_CODE","client_id":"my-agent"}'

Agent Integration (skill.md)

Any agent can integrate Uno with a single command:

shell
curl -s https://agentools.uno/v1/skill.md

This returns a Markdown guide that agents can follow to search and call tools.

Error Handling

errorMeaning
tool_not_foundTool slug doesn't exist
auth_requiredTool needs OAuth — check auth_url in response
insufficient_creditsOut of credits — check recharge_url

Pricing

  • Free: 100 credits daily, auto-reset
  • Most tools: 1 credit per call
  • AI generation tools: 5-10 credits per call