APIHub

apihub_call

Sends payment. Calls a paid endpoint on an onboarded APIHub service. Debits the endpoint's price from your credit balance and forwards the request to the upstream provider. Returns an object with the upstream response body, HTTP status, and credits_charged_microdollars. Requires a valid API key and sufficient credit balance; if balance is insufficient the call returns a 402 with payment requirements (use apihub_topup to add credits, apihub_balance to check). Use this for services already onboarded to APIHub (find slugs via apihub_search or apihub_list_services); use apihub_call_external for arbitrary x402 URLs not onboarded here, or apihub_read_content for content gateways.

Input Schema

TableJSON Schema

Name	Required	Description
`body`	No	Optional. Request body as a JSON string for POST/PUT. Ignored for GET/DELETE. The proxy forwards this verbatim with Content-Type: application/json.
`method`	No	Optional HTTP method, default GET. Must match the method declared on the endpoint or the request will fail.
`service_slug`	Yes	Required. The service slug as returned by apihub_search or apihub_list_services, e.g. 'exchange-rates' or 'weather'.
`endpoint_path`	Yes	Required. The endpoint path including any leading slash, e.g. '/latest/USD' or '/v1/forecast'. Get valid paths from apihub_get_service.

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses debit of credits, forwarding request, return object with upstream response, HTTP status, credits_charged_microdollars, and error condition (402). No contradictions since no annotations provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is front-loaded with purpose, then behavior, return, error handling, and alternatives. Each sentence adds value, though slightly long; justified by completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all aspects: purpose, usage, behavior, parameters, return, error handling, and alternatives. No output schema needed given detailed description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds meaning beyond schema by explaining body ignored for GET/DELETE, method must match endpoint, and provides examples for service_slug and endpoint_path. Schema coverage is 100%.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool sends a payment and calls a paid endpoint on an onboarded APIHub service. It distinguishes from siblings like apihub_call_external and apihub_read_content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use (onboarded services) and when not (use apihub_call_external for arbitrary x402 URLs, apihub_read_content for content gateways). Also covers prerequisites (API key, credit balance) and error handling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All APIHub tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: balance checking, service discovery (list/search/get), paid calls (internal/external), content reading, and credit top-up. Overlaps like list_services vs. search are clearly differentiated by how they are used (browse vs. filter).

Naming Consistency5/5

All tools follow a consistent `apihub_verb_noun` pattern in snake_case. Verbs like get, list, search, call, topup are paired with appropriate nouns, and modifiers like 'external' are used uniformly.

Tool Count5/5

With 9 tools, the server is well-scoped for its purpose as an API marketplace. Each tool covers a necessary part of the workflow—discovery, payment, invocation—without unnecessary duplication or missing essentials.

Completeness5/5

The tool set provides a complete lifecycle: service discovery (list, search, get), credit management (balance, topup), and API invocation (call, call_external, read_content). No obvious gaps for the intended use case.

Resources

Need Help?