Quivr App FastAPI

Name: FastAPI API
Brand: FastAPI
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource Controlbearer53 EndpointsREST

For Agents

Programmatically retrieve public brains, update existing brain secrets. Covers 53 operations with bearer authentication.

I need to public brains, I want to existing brain secrets, Search for question context for brain, Find all healthz

Install Jentic One Beta

Connect the FastAPI to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the FastAPI, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 FastAPI API.

Retrieve Public Brains

Update Existing Brain Secrets

Get Question Context For Brain

Healthz

GET STARTED

Start building with FastAPI API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use FastAPI API for, with concrete tasks.

★ Developer Tools Operations

Use the FastAPI to perform developer tools operations programmatically. The API provides 53 endpoints covering core functionality including retrieve public brains, update existing brain secrets, get question context for brain.

Call GET /brains/public to retrieve public brains

Automated Brain Management

Automate brain operations by combining multiple FastAPI endpoints. Agents can update existing brain secrets and then get question context for brain in a single workflow.

Call PUT /brains/{brain_id}/secrets-values to update existing brain secrets, then verify the result

AI Agent Integration via Jentic

AI agents discover and call FastAPI 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 bearer tokens manually.

Search Jentic for 'retrieve public brains', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

53 endpoints — open-source rag framework.

METHOD

PATH

DESCRIPTION

GET

/brains/public

Retrieve Public Brains

PUT

/brains/{brain_id}/secrets-values

Update Existing Brain Secrets

POST

/brains/{brain_id}/documents

Get Question Context For Brain

GET

/chat/healthz

Healthz

POST

/chat

Create Chat Handler

GET

/chat

Get Chats

DELETE

/chat/{chat_id}

Delete Chat

PUT

/chat/{chat_id}/metadata

Update Chat Metadata Handler

GET

/brains/public

Retrieve Public Brains

PUT

/brains/{brain_id}/secrets-values

Update Existing Brain Secrets

POST

/brains/{brain_id}/documents

Get Question Context For Brain

GET

/chat/healthz

Healthz

POST

/chat

Create Chat Handler

GET

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

FastAPI bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'retrieve public brains') and Jentic returns the matching FastAPI operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct FastAPI integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using FastAPI API through Jentic.

What authentication does the FastAPI use?

The FastAPI uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I retrieve public brains with the FastAPI?

Yes. Use the GET /brains/public endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the FastAPI?

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 retrieve public brains through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'retrieve public brains'. Jentic returns the matching FastAPI operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the FastAPI have?

The FastAPI exposes 53 endpoints covering brain, chat, health operations.