Skip to main content
Rock API, also written as RockAPI, is the AI API gateway and OpenAPI marketplace at rockapi.ai. Use the dashboard to manage API keys, review available services, inspect usage, and track billing. Use this documentation to configure a client and understand the behavior of the interfaces you call.

​
What the platform provides

The model gateway routes supported requests to configured upstream providers. An OpenAI-compatible client can use this base URL for supported interfaces:
The gateway also has provider-specific adapters and request conversion paths. This does not make every upstream model or feature available through every interface. Check the model catalog for the model ID, available group, price unit, and current conditions before integrating. The Models and providers guide explains how to evaluate model access. The OpenAPI marketplace provides access to listed API services under their own subscription plans and terms. Review the selected service’s interface, authentication requirements, usage limits, and subscription conditions separately from model token pricing.

​
Validate compatibility before migrating

For a supported OpenAI-style call, configure your Rock API key and the base URL: Python SDK clients use base_url, while Node.js SDK clients use baseURL. Also select an available model ID and confirm that your endpoint, request fields, and response handling are supported. Changing the URL alone does not establish compatibility. Validate the features your application uses, including streaming, tool calls, structured output, or media input where applicable. Follow the OpenAI-compatible API guide, then test with a small request before moving production traffic.

​
Send your first request

  1. Create an account and sign in to the dashboard. Check your available balance or applicable plan before calling a paid service.
  2. Open API keys, create a key for the application, and store it on your server. Review Authentication for credential handling.
  3. Choose a model from the current catalog. Record its exact ID, the group you will use, the supported interface, and the billing unit.
  4. Configure your client with the key and base URL. Follow the Quickstart with a short, non-sensitive request, using the model you selected.
  5. Inspect the returned content and usage information. Match the call to its dashboard usage entry and compare the settled charge with the applicable pricing rule. Keep the request ID for troubleshooting.

​
Check cost and data handling

Prices depend on the model, group, and applicable billing rules. Consult Pricing and billing for usage-based, per-call, and dynamic charges. A displayed base price or a price for one model is not a universal discount or a quote for every call. Requests pass through the gateway to an upstream service. Read Security and privacy before handling sensitive content, and confirm retention, training use, or regional requirements for your actual route. If a call fails, use Errors and rate limits to check the response and choose the next action.

​
Official domains and support

The dashboard and service catalog are hosted at rockapi.ai; documentation is hosted at docs.rockapi.ai. For account, service, or privacy questions, use the support channel listed on the main site’s About page. Include a request ID and a redacted description rather than your full API key or private request content.