Access the MCP/API technical reference

In short

The help center explains connection and use; the versioned technical reference remains on developer.billabex.com. Use it for the endpoint, Streamable HTTP transport, OAuth, scopes, input and output schemas, and errors. Do not copy a tool catalog into an integration: discover the capabilities currently exposed by the server.

Expected result

Your integration follows the current reference and discovers server capabilities instead of relying on a copied list.

Before you start

Use a remote MCP client compatible with the authentication described in the reference.
Prepare a test environment and organization without sensitive data.

Procedure

Open the MCP guide on developer.billabex.com from this article’s developer link.
Follow its transport, authentication, and permission sections without inferring the contract from this help article.
Discover tools, prompts, and resources at runtime, then validate their schemas before every call.
Reproduce the documented test cases and errors with a dedicated organization.
Record the client version and revalidate the integration when the reference announces a protocol change.

What Billabex does

The developer reference is the single technical contract for transport, authentication, schemas, and errors. The help center does not duplicate that contract, preventing a copied version from becoming stale as the server evolves.

If the result is not what you expected

If this article differs from the developer reference, follow the versioned reference.
Validate discovered schemas instead of guessing parameters from a tool name.
For a reproducible report, provide client version, time, method, status, and a redacted error body.