canonical: https://jentic.com/apis/congressionalstockbrain.com/congressionalstockbrain

# Congressionalstockbrain Base44 App Management API

The Base44 App Management API manages the data and configuration behind a Base44 application, including the backend for congressionalstockbrain.com. It lists, counts, creates, and updates records of any entity the app defines, administers app users, and manages apps, folders, workspaces, members, and external integrations. Entity records are reached under an app id and an entity name, so an agent can read and write a Base44 app's data without the app front end. Authentication uses a personal access token as a bearer, or a workspace API key sent in the api_key header.

## For AI agents

List, count, create, and update records of any entity in a Base44 app, administer app users, and manage apps, folders, and workspace members through the Base44 App Management API.

## Scope

Does not handle payment processing, email delivery, or front-end hosting. Use for managing a Base44 app's data entities, users, and workspace configuration only.

## Capabilities

- List and count records of any entity a Base44 app defines
- Create and update entity records under a given app
- Read and update the app's user records
- Administer apps and organize them into folders
- Manage workspace members, groups, and invitations
- Connect external integrations available to an app

## Use cases

### Agent-Driven App Data Access

An AI agent connected through Jentic can read and extend a Base44 app's data without the app's front end: it lists the records of a named entity and creates a new record from information it has gathered. Because entity access is scoped by app id, the agent works against one app's data at a time.

Example prompt: List the records of a named entity in the app and create a new entity record

### Entity Querying

Reporting over app data starts with a filtered query. The count operation returns how many records of an entity match a query, and the list operation returns a page of them with chosen fields, so an agent can size a result set before pulling the rows it needs.

Example prompt: Count the records in an entity that match a query, then list the first page of them

### User Administration

App operators need to keep user records current. The API reads a single app user by id and updates the stored fields on that user, so an agent can look up a user and correct or enrich their record as part of a support or onboarding flow.

Example prompt: Get an app user by id and update their stored fields

### Workspace Setup

Standing up a team on the platform involves people as well as data. The API invites members to a workspace and lists the current members and groups, so an agent can automate onboarding a workspace and report who currently has access.

Example prompt: Invite a new member to a workspace and list the current members

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/apps/{app_id}/entities/{entity_name}/v2/list` | List records of an entity |
| POST | `/api/apps/{app_id}/entities/{entity_name}` | Create an entity record |
| GET | `/api/apps/{app_id}/entities/{entity_name}/count` | Count records of an entity |
| GET | `/api/apps/{app_id}/entities/User` | List app users |
| GET | `/api/apps/{app_id}/entities/User/{user_id}` | Get an app user |
| PUT | `/api/apps/{app_id}/entities/User/{user_id}` | Update an app user |

## Key resources

- **Entities** — List, count, create, and update records of any entity an app defines
- **App Users** — Read, update, and remove the users of an app
- **Apps and Folders** — Administer apps, folder trees, and platform settings
- **Workspace** — Manage workspace members, groups, and invitations

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 59 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 83 / 100
  - Developer Experience & Jentic Compatibility: 72 / 100
  - AI-Readiness & Agent Experience: 56 / 100
  - Agent Usability: 43 / 100
  - Security: 55 / 100
  - AI Discoverability: 78 / 100
- **View full report:** https://jentic.com/apis/congressionalstockbrain.com/congressionalstockbrain/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Base44 App Management API by hand means handling two credential types, a bearer personal access token and a workspace key in the api_key header, and nesting every data call under an app id and entity name. Through Jentic you install once, import it from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Base44 puts the app id in the URL path (`/api/apps/{app_id}/...`), so a rule can pin your agent to one app: it can read that app's entity records and nothing else. You choose the operations it may call, so writes like creating records or removing users are not included unless you add them.
- **Credential handling:** Your Base44 token or workspace key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list records of an app entity' or 'get an app user', and Jentic returns the matching Base44 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Supabase** — Supabase is a backend platform with a Postgres database and auto-generated data APIs.
- **Backendless** — Backendless is a backend-as-a-service for app data, users, and logic.
- **Firebase** — Firebase offers hosted databases, auth, and app services for mobile and web apps.
- **Airtable** — Airtable stores structured records in shareable tables an agent can read alongside app data.

## FAQ

### What authentication does the Base44 App Management API use?

The Base44 App Management API accepts a personal access token sent as an Authorization bearer token, or a workspace API key sent in the api_key header, per its OpenAPI spec. When you call it through Jentic, that credential is stored once by your own Jentic One instance and injected at execution time, so it never reaches the agent's prompt or logs.

### Can I read a custom entity's records with the Base44 App Management API?

Yes. The entity list and count operations work against any entity the app defines, addressed by app id and entity name, and accept a query, field selection, sort, and paging, so an agent can read the records of a custom entity the same way it reads the built-in User entity.

### What are the rate limits for the Base44 App Management API?

The OpenAPI spec does not define numeric rate limits for the Base44 App Management API. Check the Base44 documentation at https://docs.base44.com for the current request limits that apply to your token.

### Can I limit what my agent is allowed to do with the Base44 App Management API?

Yes. Base44 puts the app id in the URL path, so write a rule that allows only the entity list and count operations for one app: the agent can then read that app's records but cannot create records, update users, or change workspace members, and every call it makes is logged.

### How do I read an app's entity records with the Base44 App Management API through Jentic?

Search Jentic with an intent like 'list records of a Base44 app entity', and Jentic returns the entity list operation at `/api/apps/{app_id}/entities/{entity_name}/v2/list` with its input schema so your agent passes the app id and entity name. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Is there a Base44 MCP server?

You don't need an MCP server to give your agent the Base44 App Management API. Jentic connects it directly from the API Directory: import the API, store your token once, and your agent calls the entity, user, and workspace operations on demand.