Skip to main content

Auth & Access

FastNear API keys solve two different problems:

  1. Quick docs-side demos where you want the embedded examples to run with your account limits.
  2. Production backend access where your service, agent runner, or proxy must own the credential lifecycle.

Treat those as separate tracks.

Choose your track​

  • Browser Demo: use the in-browser docs flow to try requests quickly. This is for demos, local development, and personal exploration.
  • Production Backend: keep keys on the server side, inject them from env vars or secret stores, and never expose them to browsers.

In-browser demo setup​

Use the built-in manager below when you want the docs examples to run with your FastNear account limits:

API Key Configuration

Set your FastNear API key here. It will be automatically included in all RPC documentation examples.

What this page is and is not​

  • This page is the fastest way to exercise authenticated docs examples and understand the available auth tracks.
  • This page is not a recommendation to store production credentials in browser localStorage.
  • If your code runs in a browser, extension, or public client app, treat the credential as exposed.

Getting an API key​

  1. Visit FastNear Subscriptions.
  2. Choose a plan that fits your workload.
  3. Generate your API key in the FastNear dashboard.
  4. Use the browser-demo track only for local docs exploration.
  5. Move production traffic to the backend track before shipping.

When you need more than a demo​

  • Use Production Backend for env vars, proxy patterns, redaction, and rotation.
  • Use Auth for Agents when an agent runner or automation service needs FastNear access.