The API Catalog is the RichAPI dashboard page that lists every endpoint your workspace can call. Each card shows the endpoint name, a short description, the category, and the credit price. The Try It button on a card sends a real request from the browser and spends real credits from the workspace.

The API Catalog lists one card for each endpoint that your workspace can call. RichAPI builds the list from the endpoints that your API key unlocks, so two workspaces can see two different lists. The page shows no endpoint that your workspace cannot call. A counter above the cards reads <shown> of <total> apis, and a badge next to it names your plan.

RichAPI prices an endpoint in one of the shapes below. The shape decides what one call costs, so read it before you run anything. 1 credit costs $0.02 on the 1,000 and 5,000 credit packs, and less on larger packs.

CAUTION: Read the unit on the card before you run an endpoint. A card that ends in /RESULT charges for every result, so a high limit costs more.

One Profile Enrichment call costs 1 credit. One People Search call that returns 100 results costs 10 credits. That is 10 times the price of the flat-rate call.

The search box matches three things: the endpoint name, the description, and the slug in the request line. The match ignores capital letters.

The category pills follow a fixed order: Enrichment, Search, Web Scraping, YouTube, Directory, Social, Activity, Email, AI, Ads, Utilities, System. RichAPI shows a pill only for a category that your endpoint list holds. An endpoint in another category, such as Leads, Maps or Funding Data, has no pill. Find it under All or with the search box. Lowest Cost sorts on the number printed on the card, from low to high.

When no endpoint matches, the page shows this text: "No APIs match your search. Try adjusting your filters."

CAUTION: Set the limit parameter before you click Run. Try It sends a real request through your API key and spends real credits. The dialog asks for no second confirmation. A per-result endpoint with a high limit costs far more than a flat-price endpoint.

RichAPI picks the API key for you. The workspace does not choose a key in the dialog. RichAPI uses the oldest active key in the workspace.

The parameter fields come from the parameter list of the endpoint. RichAPI builds one field for each parameter and marks a required parameter with a red asterisk after its name.

The grey hint is a hint, not a value. RichAPI leaves an empty field out of the request body, so an empty optional field sends no parameter. The Run button stays disabled until every required field holds a value.

RichAPI holds the full price of the call before it starts. A response with a status of 400 or higher charges no credits, because RichAPI returns the whole amount. A per-result call that returns fewer results than the limit charges less than the amount held.

Endpoint access belongs to the organization and the workspace, not to the member.

An endpoint that your workspace cannot call does not appear on the page at all. There is no locked card and no upgrade prompt. If an endpoint that a colleague names is missing from your API Catalog, the endpoint is not enabled for your workspace.

To ask for access to an endpoint, write to [email protected]. Name the workspace and the endpoint. After RichAPI changes the access of a workspace, the change takes up to five minutes to reach every server. Reload the API Catalog page after five minutes.

If a call reaches a blocked endpoint, RichAPI returns 403 with the message Endpoint not available on your plan. GET /api/v1/my-endpoints lists the endpoints a key can use.

The dashboard home page carries a smaller runner, named Quick Runner. It runs the same call as Try It and spends the same credits.

The Recent Runs card on the right lists your last calls. Click a row to load that endpoint with the same parameters. The Explore card lists endpoints on your plan that you have not tried, each with a Try button.

The API Catalog card is a summary. It holds no parameter table and no response example.

Every RichAPI endpoint has its own article, with a parameter table, a response example, cURL, Python, and Node.js samples, and an error table. The View Docs button on a card opens the in-app Documentation page at /home/<workspace-slug>/docs for the same endpoint.

Yes. Try It sends a real request through the API key of the workspace, and RichAPI bills the workspace for it. The dialog asks for no second confirmation, so the call starts as soon as you click Run. Set every limit parameter to a small number first.

RichAPI prices an endpoint per call or per result. A per-call endpoint charges the same price for every call. A per-result endpoint multiplies its price by the number of results, so a high limit produces a high charge. People Search at a limit of 100 costs 10 credits when it returns 100 results, and Profile Enrichment costs 1 credit.

The API Catalog lists only the endpoints that your workspace can call. An endpoint that RichAPI does not enable for your workspace is hidden, not locked. Write to [email protected] to ask about access, and name the workspace and the endpoint.

No. RichAPI picks the oldest active key in the workspace and shows its prefix in the dialog. To change the key that Try It uses, revoke the older key on the API Keys page.

No. The dialog reads the key of the workspace on the server and never shows the full key. The dialog shows only the key prefix. A direct API call from your own code still needs the x-api-key header.

Lowest Cost sorts on the credit number printed on each card, from low to high. For a per-result endpoint, that number is the price of one result. A per-result endpoint therefore sorts near the top, even with a full-call price above a flat-price endpoint.

No. RichAPI holds the price of the call before it starts. If the status code is 400 or higher, RichAPI returns the whole amount to the workspace. Only a status code between 200 and 299 charges credits.

Next: How Waterfall Enrichment Works and When You Are Charged