Skip to main content

​
Pricing

A personal organization starts with 500 free credits. One successful tool execution costs one credit; failed runs and test runs from the editor are free. Once the free credits are used up, credits are purchased in packages from the Credits page (Credits).
The organization that executes the tool. Credits are always deducted from the caller’s balance; the provider of a public ToolSet is never charged.
No. Credits never expire.

​
Technical

Python and TypeScript. The language is chosen when the ToolSet is created and cannot be changed afterwards.
Yes. Add them on the ToolSet’s Packages tab, optionally pinning a version. Packages are installed into the sandbox; for TypeScript ToolSets zod and tsx are always available. Publish a new version for API calls to pick up changed packages (ToolSet Management).
The timeout is set per ToolSet. The default is 900 seconds (15 minutes) and the maximum is 3,600 seconds (1 hour).
As environment variables on the ToolSet’s Environment tab, with the Secret switch on. Secret values are encrypted and masked, and are available to the code through os.environ or process.env (Managing Environment Variables).

​
Troubleshooting

  1. Open Runs and check the failed run’s error, stdout and stderr (Execution & Testing).
  2. Verify the input and the environment variables of the environment profile the call used.
  3. Reproduce the problem from the tool editor’s Test panel; after a failed test, Auto Fix Error in the Coding Agent panel proposes a fix (Tool Development).
  • Make sure the full key was copied. The list only shows a masked prefix; for keys created after key encryption was introduced, the copy button next to it retrieves the full key again.
  • Check that the key belongs to the organization whose ToolSet you are calling, or that the ToolSet is public.
  • Check what is published. A call to your own organization’s ToolSet runs the version published for the key’s environment profile; a call to another organization’s public ToolSet runs the version in the provider’s default environment. The public endpoints refuse the call with 400 and “No published version available” when nothing is published there.
  • If in doubt, create a new key and delete the old one (API Key Management).
A private ToolSet can only be executed with an API key of the organization that owns it. Other organizations receive an error even with a valid key. Make the ToolSet public, or use a key from the owning organization.
The registry only lists ToolSets that have a published version for the API key’s environment and contain at least one tool. Publish a version for that environment, then Sync the registry in Jinba Flow (Jinba Flow Integration).