For Agents
Programmatically create a new user., get users by query.. Covers 194 operations with openIdConnect authentication.
Use for: I need to a new user., I want to users by query., Search for a user by id., Find all a user.
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
squidex.io/main version 7.0.0.0. The API exposes 194 endpoints secured with openIdConnect authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Squidex 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%2Fsquidex.io%2Fsquidex" | shStep 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%2Fsquidex.io%2Fsquidex" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Squidex API.
Create a new user.
Get users by query.
Update a user.
Delete a User.
Lock a user.
Unlock a user.
Patterns agents use Squidex API for, with concrete tasks.
★ Developer Tools Operations
Use the Squidex API to perform developer tools operations programmatically. The API provides 194 endpoints covering core functionality including create a new user., get users by query., get a user by id..
Call POST /api/user-management to create a new user.
Automated Apps Management
Automate apps operations by combining multiple Squidex API endpoints. Agents can get users by query. and then get a user by id. in a single workflow.
Call GET /api/user-management to get users by query., then verify the result
AI Agent Integration via Jentic
AI agents discover and call Squidex API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle openIdConnect tokens manually.
Search Jentic for 'create a new user.', load the operation schema, and execute with Jentic-managed credentials
194 endpoints — squidex.
METHOD
PATH
DESCRIPTION
/api/user-management
Create a new user.
/api/user-management
Get users by query.
/api/user-management/{id}
Get a user by ID.
/api/user-management/{id}
Update a user.
/api/user-management/{id}
Delete a User.
/api/user-management/{id}/lock
Lock a user.
/api/user-management/{id}/unlock
Unlock a user.
/api
Get the user resources.
/api/user-management
Create a new user.
/api/user-management
Get users by query.
/api/user-management/{id}
Get a user by ID.
/api/user-management/{id}
Update a user.
/api/user-management/{id}
Delete a User.
/api/user-management/{id}/lock
Lock a user.
/api/user-management/{id}/unlock
Unlock a user.
/api
Get the user resources.
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Squidex by hand means running its OpenID Connect flow against cloud.squidex.io and managing user-management calls yourself. Through Jentic you install once, import the Squidex API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Squidex puts the user id in the URL path (/api/user-management/{id}), so a rule can pin your agent to reading a single user. You choose the operations it may call, so ones like deleting, locking, or unlocking a user are not included unless you add them.
Credential isolation
Your Squidex credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list managed users' or 'look up a user by id', and Jentic returns the matching Squidex operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Specific to using Squidex API through Jentic.
What authentication does the Squidex API use?
The Squidex API uses openIdConnect authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I create a new user. with the Squidex API?
Yes. Use the POST /api/user-management endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Squidex API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create a new user. through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new user.'. Jentic returns the matching Squidex API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Squidex API have?
The Squidex API exposes 194 endpoints covering apps, assets, content operations.
GET STARTED