Skip to main content
The Memic public API is a small, focused REST surface for ingesting, searching, and chatting over your data. Every endpoint is scoped to an environment via a single API key — no organization, project, or environment IDs in the URL.

​
Base URL

https://api.memic.ai/api/v1
All endpoints are relative to this base. Examples in this reference use the full URL for clarity.

​
The 10 endpoints

Context

GET /me — Return the org/project/environment resolved from your key.

Projects

GET /projects — List all projects in your organization.

Search

POST /search — Run semantic search scoped to your environment.

Chat

POST /chat — Grounded chat over your indexed documents.

Files

GET /files, POST /files/init, POST /files/{id}/confirm, GET /files/{id}/status, DELETE /files/{id}

Prompts

GET /prompts/{name} — Fetch the live version of a managed prompt.

​
Conventions

  • JSON in, JSON out. Request bodies are application/json. Responses are UTF-8 encoded JSON.
  • UUIDs are used for all resource identifiers (file_id, project_id, etc.) in the canonical 8-4-4-4-12 format.
  • Timestamps are ISO 8601 in UTC: 2026-04-12T14:23:05.123Z.
  • Pagination is cursor-less and uses page + page_size query params where applicable. See Pagination.
  • Errors follow RFC 7807 problem details. See Errors.

​
Next

Authentication

How API keys work.

Errors

Error codes and response format.

Rate limits

What to expect under load.