How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Agno Knowledge API

The Knowledge API from Agno — 8 operation(s) for knowledge.

Agno Knowledge API is one of 28 APIs that Agno publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Knowledge. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 12 operations across 8 paths, and defines 26 schemas. It is described by OpenAPI 3.2.0, at version 2.5.6.

Requests are made against a single base URL, https://api.agno.com.

12 operations 8 paths 26 schemas 2 DELETE6 GET1 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.5.6
Base URL
https://api.agno.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Agno Knowledge API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (HTTPBearer).

Paths & Operations 12

Across 8 paths, the API surfaces 12 operations — 2 DELETE, 6 GET, 1 PATCH, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Knowledge 12
POST
/knowledge/content
Upload Content
upload_content 2 params body → 202400401404422500
GET
/knowledge/content
List Content
get_content 6 params → 200400401404422500
DELETE
/knowledge/content
Delete All Content
delete_all_content 2 params → 200400401404422500
POST
/knowledge/remote-content
Upload Remote Content
upload_remote_content 2 params body → 202400401404422500
PATCH
/knowledge/content/{content_id}
Update Content
update_content 3 params body → 200400401404422500
GET
/knowledge/content/{content_id}
Get Content by ID
get_content_by_id 3 params → 200400401404422500
DELETE
/knowledge/content/{content_id}
Delete Content by ID
delete_content_by_id 3 params → 200400401404422500
GET
/knowledge/content/{content_id}/status
Get Content Status
get_content_status 3 params → 200400401404422500
POST
/knowledge/search
Search Knowledge
search_knowledge body → 200400401404422500
GET
/knowledge/config
Get Config
get_knowledge_config 2 params → 200400401404422500
GET
/knowledge/{knowledge_id}/sources
List Content Sources
list_content_sources 2 params → 200400401404422500
GET
/knowledge/{knowledge_id}/sources/{source_id}/files
List Files in Source
list_source_files 7 params → 200400401404422500

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are ContentResponseSchema (12 properties), Body_upload_content (10 properties), Body_upload_remote_content (9 properties), VectorSearchResult (9 properties). Each schema is shown below with its type and property counts.

PaginatedResponse_ContentResponseSchema_
object
2 properties 2 required
VectorSearchRequestSchema
object
Schema for vector search request.
8 properties 1 required
ChunkerSchema
object
4 properties 1 required
Body_upload_content
object
10 properties
ValidationErrorResponse
object
2 properties 1 required
NotFoundResponse
object
2 properties 1 required
Meta
object
Inline metadata schema for pagination.
2 properties
PaginationInfo
object
5 properties
Body_update_content
object
4 properties
Body_upload_remote_content
object
9 properties 2 required
SourceFileSchema
object
Schema for a file in a content source.
5 properties 2 required
VectorSearchResult
object
Schema for search result documents.
9 properties 2 required
SourceFilesResponseSchema
object
Response schema for listing files in a content source.
6 properties 3 required
PaginatedResponse_VectorSearchResult_
object
2 properties 2 required
VectorDbSchema
object
4 properties 1 required
InternalServerErrorResponse
object
2 properties 1 required
SortOrder
string
ContentStatus
string
Enumeration of possible content processing statuses.
ReaderSchema
object
4 properties 1 required
ContentStatusResponse
object
Response model for content status endpoint.
3 properties 1 required
BadRequestResponse
object
2 properties 1 required
RemoteContentSourceSchema
object
Schema for remote content source configuration.
5 properties 3 required
ConfigResponseSchema
object
6 properties
SourceFolderSchema
object
Schema for a folder in a content source.
3 properties 2 required
UnauthenticatedResponse
object
2 properties 1 required
ContentResponseSchema
object
12 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

agno-knowledge-api-openapi.yml Raw ↑

Other APIs Agno publishes across the network.

Agno A2A API
Agno Agents API
Agno AGUI API
Agno Approvals API
Agno Components API
Agno Core API
Agno Database API
Agno Evals API
Agno Health API
Agno Home API
Agno Memory API
Agno Metrics API
Where this information came from

This is an independent, third-party profile of Agno Knowledge API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.