Install Jentic One Beta

Connect the Base44 App Management API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Base44 App Management API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcongressionalstockbrain.com%2Fcongressionalstockbrain" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcongressionalstockbrain.com%2Fcongressionalstockbrain" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Base44 App Management API.

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

GET STARTED

Start building with Base44 App Management API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Base44 App Management API for, with concrete tasks.

★ 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.

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.

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.

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.

Invite a new member to a workspace and list the current members

Key Endpoints

411 endpoints — the base44 app management api manages the data and configuration behind a base44 application, including the backend for congressionalstockbrain.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Base44 App Management API through Jentic.

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.

Congressionalstockbrain Base44 App Management API

AI ReadinessFoundational (C+)59/100

See full scorecard

Official vendor OpenAPI document · agent-readyStorageDatabasebearer, apiKey411 EndpointsREST

For 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.

Use for: List all records of a custom entity in an app, Create a new entity record in a Base44 app, Count the records matching a query in an entity, Get an app user by id

Not supported: 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.

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

89%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

42%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

39%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

52%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4

72%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

99%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

54%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: D-Signals: 1

43%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: CSignals: 1

55%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

78%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Base44 App Management API to your agent

Capabilities

Start building with Base44 App Management API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Congressionalstockbrain Base44 App Management API

Jentic AI Readiness Score

Base44 App Management API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness