agentleFS
fusebase-devfusebase-dev/fusebase-flow/.agents/skills/api-exploration/SKILL.md

api-exploration

Skill9 starsChanged 27 days agoMITView on GitHub

Workflow for testing Fusebase API calls interactively using temporary tokens. Use when: 1. You need to verify an API endpoint behavior before writing app code, 2. You want to explore available API responses or schemas, 3. You're unsure how an API endpoint works and need to test it, 4. Debugging API integration issues by making direct calls.

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When you're unsure about an API endpoint's behavior, response shape, or want to test a flow before committing to implementation — create a …

    line 8
  2. Very specific:

    Create a temporary script (e.g.

    line 28
  3. Distinctive:

    Read the output, adjust your calls, and re-run.

    line 48
  4. Distinctive:

    Delete the temporary test script when done — don't commit it.

    line 52
  5. Distinctive:

    Use this to verify SDK calls before wiring them into app UI code.

    line 56
  6. Distinctive:

    Use this for any Fusebase API call you want to validate — dashboard data, app endpoints, etc.

    line 102

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

API Exploration with Temporary Tokens

When you're unsure about an API endpoint's behavior, response shape, or want to test a flow before committing to implementation — create a temporary token and run test calls directly.

Workflow

1. Create a temporary token

fusebase token create --app <appId>

This outputs a short-lived token (15 min) to stdout. Capture it:

TOKEN=$(fusebase token create --app <appId>)

The appId comes from fusebase.json → apps[].id.

2. Write and run test code

Create a temporary script (e.g. _test-api.ts) to make the API calls you want to verify:

const token = process.env.TOKEN || "<paste-token-here>";

const res = await fetch("https://api-endpoint/...", {
  headers: { "x-app-feature-token": token },
});
console.log(res.status);
console.log(await res.json());

Run it:

TOKEN=$(fusebase token create --app <appId>) bun _test-api.ts

3. Inspect results and iterate

Read the output, adjust your calls, and re-run. Once you understand the API behavior, implement it properly in your app code.

4. Clean up

Delete the temporary test script when done — don't commit it.

Example: Testing @fusebase/dashboard-service-sdk

Use this to verify SDK calls before wiring them into app UI code.

_test-sdk.ts:

import {
  createClient,
  DatabasesApi,
  CustomDashboardRowsApi,
} from "@fusebase/dashboard-service-sdk";

const token = process.env.TOKEN!;
const BASE_URL =
  "https://app-api.{FUSEBASE_HOST}/v4/api/proxy/dashboard-service/v1";

const client = createClient({
  baseUrl: BASE_URL,
  defaultHeaders: { "x-app-feature-token": token },
});

const dbApi = new DatabasesApi(client);
const rowsApi = new CustomDashboardRowsApi(client);

// List databases visible to this app
const dbs = await dbApi.listDatabases({});
console.log("databases:", JSON.stringify(dbs, null, 2));

// Read rows from a specific dashboard view
const rows = await rowsApi.getRows({
  dashboardId: "<dashboardId>",
  viewId: "<viewId>",
});
console.log("rows:", JSON.stringify(rows, null, 2));

Run it:

TOKEN=$(fusebase token create --app <appId>) bun _test-sdk.ts

Replace BASE_URL host with the value matching your environment's FUSEBASE_HOST (e.g. app-api.thefusebase.com for prod).

Key Points

  • Token expires in 15 minutes. Create a new one if it expires.
  • Use this for any Fusebase API call you want to validate — dashboard data, app endpoints, etc.
  • The API spec is available at the public OpenAPI endpoint if you need to discover available routes.
  • Prefix test files with _ (e.g. _test-sdk.ts) so they're easy to spot and clean up.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.