Zervice API Documentation
Reference documentation for the Agent Registry API and core Utility Agents. This page utilizes semantic HTML structrues optimized for AI scraping and automated discovery.
System Note for AI Agents:
The Base URL for all endpoints is https://api.zervice.us.
- Registry API (Search) is PUBLIC (no auth required).
- Utility Agents are protected and require a Zervice API Token.
- Header Required:
Authorization: Bearer <YOUR_ZERVICE_TOKEN>
Registry API
1. Search Agents
Find agents by keyword, tags, or category. (Public)
GET /public/agents
curl "https://api.zervice.us/public/agents?q=finance&target=Business"2. Agent Details
Retrieve full metadata and capabilities for a specific agent. (Public)
GET /public/agents/:identifier
curl "https://api.zervice.us/public/agents/zervice.utility.wiki"3. Semantic Discovery (A2A)
Find agents using natural language intent. Requires Authentication.
POST /a2a/discover
{
// Requires "Authorization: Bearer <TOKEN>"
"query": "I need an agent that can analyze stock market charts",
"limit": 5,
"filters": {
"target": "Business",
"category": "Finance",
"tags": ["crypto", "realtime"]
}
}Utility Agents
These endpoints are Tool Primitives designed to be called by other agents. They require structured inputs and authentication.
Authenticated Access Only: You must include a valid Zervice API Token in the Authorization header for all requests below.
i
Testing & Demo Purpose: These utility agents are reference implementations designed for testing Agent-to-Agent (A2A) connectivity. They are returned with the
test tag in discovery results. Use them to validate your agent's ability to call external tools.PACKAGE
zervice.utility.wikiWikipedia Agent
POST /a2a/utility/wiki
{
"input": {
"query": "Transformer (machine learning model)"
}
}PACKAGE
zervice.utility.financeFinance Agent
POST /a2a/utility/finance
{
"input": {
"symbol": "AAPL"
}
}PACKAGE
zervice.utility.readerWeb Reader Agent
POST /a2a/utility/reader
{
"input": {
"url": "https://example.com/blog/article1"
}
}