What authentication does the Para API use?

Para API uses JWT bearer token authentication. POST /jwt_auth returns an access_token that must be included in the Authorization header for subsequent requests. Through Jentic, tokens are stored in the encrypted vault and injected at execution time.

Can I use custom object types?

Yes. The {type} path parameter accepts any custom object type (users, posts, comments, products, etc). Para stores and indexes objects flexibly, allowing you to define your own schemas and relationships.

How does pagination work?

GET /{type} accepts limit (number of results) and page (page number) query parameters. The response includes totalHits for calculating total pages. Use sort and desc parameters to control ordering.

Does Para support full-text search?

Yes. GET /search accepts a q (query string) parameter for full-text search across object fields. Optionally specify type to limit search to specific object types. Results include relevance scoring.

Is Para open-source?

Yes. Para is an open-source backend framework that can be self-hosted or used as a hosted service. The API works identically regardless of deployment model, making it suitable for both development and production.

Can I limit what my agent is allowed to do with the Para API?

Yes. Because you run Jentic One yourself, your own rules decide which Para operations and credentials the agent may use. Since Para puts the object type and id in the URL path (/{type}/{id}), a rule can pin the agent to a single object type and to specific operations, so it can create, read, list, and search those objects without touching others. Destructive calls like DELETE /{type}/{id} stay out of reach unless you explicitly grant them.