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

# Base44 UserProfile Entities API

The UserProfile Entities API reads and updates UserProfile records in a Base44 application. It retrieves UserProfile entities with filterable fields and updates a single entity by its entityId, exposing the app's user-profile data as a structured endpoint an agent can query and write to. It is scoped to one Base44 app's UserProfile collection.

## For AI agents

Read and update UserProfile records in a Base44 app: list profiles filtered by their fields and update a single profile by its entityId.

## Scope

Does not handle authentication, billing, or other Base44 entity types. Use for reading and updating UserProfile entities in one app only.

## Capabilities

- List UserProfile entities, filtered by their fields
- Fetch the current state of a profile before changing it
- Update a single UserProfile entity by its entityId

## Use cases

### AI Agent Profile Updates

An AI agent keeps a Base44 app's user profiles current without a developer writing a backend integration. Through Jentic the agent lists UserProfile entities, reads the one it needs, and updates it by its entityId, while the API key stays on the developer's own machine.

Example prompt: Fetch the UserProfile entity for a given user, change one field, and update it by its entityId

### Profile Lookup and Filtering

Workflows often need a subset of profiles that match a condition. The UserProfile Entities API returns entities filtered by their fields, so an agent can pull the profiles that match a segment before acting on them.

Example prompt: Retrieve UserProfile entities filtered to those matching a given field value and return the matching list

### Pre-Update Verification

Before writing a change, an agent should read the current profile so it does not overwrite fields it did not intend to. This API lets the agent fetch the existing UserProfile entity, inspect its fields, and then update only what changed.

Example prompt: Read a UserProfile entity, confirm a field value, and update the entity only if the value differs

## Key resources

- **UserProfile** — List UserProfile entities with filterable fields and update a single entity by its entityId

## 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:** 69 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 55 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 75 / 100
- **View full report:** https://jentic.com/apis/base44.com/base44/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 this API by hand means supplying its api_key header, learning the one app's base path, and handling the read-before-update pattern yourself. Through Jentic you install once, import the UserProfile Entities API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** A single API key reaches both operations, so a rule can allow only the read operation, letting the agent fetch profiles without writing to them. You choose which operations it may call, so the update operation is not included unless you add it.
- **Credential handling:** Your API 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 'update a user profile' or 'list profiles', and Jentic returns the matching UserProfile operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **HubSpot Contacts** — HubSpot Contacts stores and manages full contact profiles across a CRM rather than one app's UserProfile collection.
- **Salesforce** — Salesforce manages customer records across a broad CRM data model.
- **Pipedrive** — Pipedrive tracks people and deals through a sales pipeline.

## FAQ

### Is there a Base44 MCP server?

You don't need an MCP server to give your agent the UserProfile Entities API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. Operations are discovered on demand, so nothing extra loads into the agent's context.

### Can I limit what my agent is allowed to do with the UserProfile Entities API?

Yes. Write a rule that allows only the profile read operation, so the agent can list and inspect UserProfile records but cannot write changes, and add the update operation explicitly when a workflow needs to modify a profile. Every call is logged.

### What authentication does the UserProfile Entities API use?

The UserProfile Entities API authenticates with an API key sent in the `api_key` header, as declared in its OpenAPI spec. Through Jentic that key is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's prompt or logs.

### Can I filter UserProfile entities with this API?

Yes. The retrieve operation returns UserProfile entities and accepts filterable fields, so the agent can narrow the response to the profiles that match a condition rather than pulling the whole collection.

### How do I update a user profile through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then import the UserProfile Entities API from the Jentic API Directory and store your key. Your agent searches for 'update a user profile' and Jentic returns the update operation with its input schema. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### What are the rate limits for the UserProfile Entities API?

The UserProfile Entities OpenAPI spec does not define rate limits. Because the endpoint is served by one Base44 app, throughput follows that app's plan rather than a published API quota, so check your Base44 settings for current limits.