Live Catalog

Hive's release-candidate source contains 537 callable tools: 519 wrapped provider tools across 10 category-scoped MCP endpoints plus 18 Hive-native stateful monitoring, memory, alert, report, and B2B subject tools. The root /mcp endpoint keeps discovery compact; inspect the schema, choose the correctly annotated invoker, or use category/REST execution. Live discovery confirms deployed availability.

Use this page to understand the release-candidate shape. For the current production version, exact names, schemas, operations, required parameters, and pagination cursors, use the live discovery surfaces below instead of copying a cached static table.

Discovery examples

Search by the task your agent is trying to complete, not only by a guessed endpoint name.

curl -X GET "https://mcp.hiveintelligence.xyz/api/v1/tools?search=wallet%20risk&limit=5&fields=name,title,description,inputSchema" \
  -H "Authorization: Bearer YOUR_HIVE_API_KEY"

Useful first searches:

After search, call get_api_endpoint_schema before execution. That is the main difference between Hive as an agent workflow surface and a static endpoint catalog.

Authoritative discovery surfaces

REST catalog

curl -X GET "https://mcp.hiveintelligence.xyz/api/v1/tools?limit=250" \
  -H "Authorization: Bearer YOUR_HIVE_API_KEY"

Useful query parameters:

MCP resources

Read these from the root /mcp endpoint:

• hive://tools: full live tool inventory
• hive://categories: category namespaces and endpoint paths
• hive://providers: active provider integrations
• hive://toolsets: task-oriented routing maps
• hive://task-canaries: representative calls for coverage checks
• hive://skills: skill pack metadata
• hive://status: runtime status semantics

Schema lookup

Use get_api_endpoint_schema on the root /mcp endpoint before invoking any exact tool. Its result declares the operation and call pattern: reads use invoke_api_endpoint; explicitly approved Hive-native writes use invoke_stateful_endpoint.

Category inventory

Hive-native stateful tools

The 18 Hive-native tools are not part of a provider category count. They add persistence and partner-scoped state on top of the provider catalog:

• Monitors: hive_create_monitor, hive_list_monitors, hive_get_monitor, hive_update_monitor, hive_archive_monitor, hive_get_monitor_runs
• Observations and alerts: hive_list_observations, hive_list_alerts, hive_update_alert_status, hive_get_latest_snapshot
• Memory and reports: hive_remember_fact, hive_list_memory_facts, hive_forget_memory_fact, hive_generate_monitor_report
• B2B subjects: hive_list_subjects, hive_get_subject, hive_archive_subject, hive_list_subject_audit_events

Root discovery tools

The release-candidate root /mcp endpoint exposes these five workflow tools to keep general-purpose agents focused:

• search_tools
• get_api_endpoint_schema
• invoke_api_endpoint
• invoke_stateful_endpoint
• validate_task_result

search_tools, schema lookup, and task-result validation do not consume execution credits. The two invokers are the material execution boundary. Category inventories remain available through resources and the ten scoped MCP endpoints, so broad coverage does not consume root model context.

Agents should start at root unless they are intentionally constrained to one category. Focused agents can connect directly to one or more category endpoints.

Recommended workflow

1. Call search_tools with the user's natural-language task; the default compact result is bounded and paginated.
2. Read hive://toolsets/{id} for the exact workflow, execution budget, fallback, stop conditions, and output schema.
3. Call get_api_endpoint_schema for the selected exact tool.
4. Follow its declared operation: use invoke_api_endpoint for reads or invoke_stateful_endpoint for an explicitly approved Hive state change. REST /api/v1/execute remains available for backend-owned execution.
5. Call validate_task_result on the final task envelope when supported. This checks structure; it does not make invented receipts authentic.
6. Report provider-native evidence time when available, Hive retrieval/cache timing, runtime status, receipt ID/version, and any non-ok provider state.

Example agent routing:

Related

• Tools Overview
• Get Started
• Portfolio & Wallet
• MCP Features
• API Integration