RPCX Dashboard
See your compute units, buy CU, manage the MCP key, write, validate, run, and save methods, export results, and watch usage.
Everything in RPCX is managed from the RPCX page in the dashboard. The settings belong to the workspace, so every member sees the same compute units, key, methods, and usage.
Who can do what
Running a method also needs an active Pro, Ultra, Max, or Enterprise plan. Without one, Run is unavailable and the page says why.
Compute units
The top of the page has one Compute units panel. RPCX is prepaid: runs use CU you already have, and usage never charges your wallet.
On the left:
- The big number is the CU available: the plan CU left this month plus the CU you bought.
- Under it are the two sources. From your plan shows the plan CU left this month with a meter and the reset date, for example 18,000 of 20,000 plan CU left this month, resets Dec 1. The allowance resets on the 1st of every month at 00:00 UTC. Unused allowance does not carry over. Bought CU shows the CU you bought, which never expire, and how many were used this month.
- Runs use your plan CU first, then bought CU.
On the right:
- Credits shows the balance of your shared NoLimitNodes wallet, the same wallet other pay-as-you-go products use, and about how many CU it can buy at $1 per 1,000 CU. Add credits opens the panel to add credits by card or crypto. You get an email when your credits run low.
- Buy more CU has one choice: 1,000, 5,000, or 25,000 CU ($1, $5, or $25), or Custom. A custom amount is a whole number of CU, a multiple of 100, from 1,000 to 1,000,000 CU per purchase. The line under it shows the price, for example 5,000 CU for $5.00, and Buy CU buys it from your credits after you confirm. When your credits do not cover the price, Buy CU is disabled: add credits first.
Bought CU never expire and cannot be turned back into credits. RPCX takes credits only when you select Buy CU.
When the plan CU and the bought CU are both used up, the panel says No CU left: runs are refused. Buy CU to continue. Runs work again as soon as you buy CU, or on the 1st when the allowance resets. See Plan allowance and bought CU.
Your methods
The first screen lists your saved methods by their call name, rpcx_<name>, with their params and the date they were last saved.
- Search filters the list by name.
- New Method opens an empty method.
- Select a method, or its edit icon, to open it.
- The delete icon removes every version of the method. Calls to it fail from then on.
A method saved before the method language is marked Old format. It still runs when called, but it opens read-only and cannot run from the dashboard. To change it, write it again as a new method.
The method screen
The method screen works like an API client. At the top is the method name. On a new method, select Untitled method to name it. A name is 1 to 64 letters, digits, or underscores.
Below the name is the request bar:
- RPCX
rpcx_<name>: the name you call the method by. The copy button copies it. - Validate: checks the method and marks each problem in the code. It is free and runs nothing. It shows no cost estimate.
- Run: calls the saved method as
rpcx_<name>with the test values in Params, using one of your workspace's API keys, and shows the result. It shows Executing... while it runs. Each run is billed. Ctrl+Enter also runs it.
Save stores the method. Saving the same name again creates a new version and makes it active. Run needs a saved method: a new method, or one with unsaved changes, shows Save the method before running it. Save first, then run.
Code
The Code tab is an editor for the method's pipeline. A new method starts with a short example you can change.
- It completes table names, columns, params, and functions as you type. Type
fromto see the nine live tables. - It checks the code as you type. A problem gets a red underline and an icon at the start of the line. Hover the underline to read the message.
- Paste a whole method, header included, from your coding agent. The name and params fill in, and the editor keeps the pipeline.
See Writing methods for the language, and the Method language reference for every step and function with an example.
Params
The Params tab has one row per param:
Params are created from the code. When the code uses a name that is not a column of the table, a row for it appears, marked from code, with a guessed type. Check the type. When the code stops using the name, the row goes away again, unless you edited it. To add a param by hand, type its name in the empty last row.
Response
After a run, the response shows Rows, Cost in CU, Time, and the request id. Show the rows as Table, JSON, or CSV.
When your plan CU and your bought CU are used up, Run shows Allowance used up with a Buy CU link instead of a result. The run costs nothing.
A run shows up to 1,000 rows. Export saves the result as a file: CSV from the Table or CSV view, JSON from the JSON view. When the result has 1,000 rows or fewer, Export saves the rows you already have and nothing runs again. When the result is bigger, the button reads Export (runs again, billed): it runs the method text again to get every row, and that run is billed. An export holds up to 5,000,000 rows, so use it for results larger than the 10,000 rows a JSON-RPC call returns.
MCP key
In Use with an AI agent, Generate key creates the MCP key your coding agent uses, with a ready command to add it to Claude Code. The key is shown once. Regenerate replaces it and Revoke stops it. See RPCX MCP server.
Usage
The usage figures update every 10 seconds:
- CU this month, with the price per 1,000 CU
- Runs, last hour
- Recent runs: the most recent calls, with when they ran, method, status, CU, and run time
Calls that were refused, for example because the budget was used up or the plan CU and bought CU were used up, appear in the list with 0 CU.