Papr Memory API (1.0.0)

API for managing personal memory items with authentication and user-specific data.

Authentication

This API supports three authentication methods:

  • API Key: Include your API key in the X-API-Key header
    X-API-Key: <your-api-key>
  • Session Token: Include your session token in the X-Session-Token header
    X-Session-Token: <your-session-token>
  • Bearer Token: Include your OAuth2 token from Auth0 in the Authorization header
    Authorization: Bearer <token>

All endpoints require one of these authentication methods.

Download OpenAPI description
Languages
Servers
Production server
https://memoryserver-staging-223473570766.us-west1.run.app/

v1

Operations

Extract metadata only (for on-device transform)

Request

Extracts frequency metadata from text content without requiring an embedding. Returns metadata + phases that can be used with the on-device SDK for local transforms. Call this once per document at index time, then use phases locally for scoring.

Bodyapplication/jsonrequired
contentstring(Content)required

Text content for metadata extraction

domainDomain (string) or Domain (null)(Domain)

Domain for frequency schema

Default "general"
Any of:

Domain for frequency schema

string(Domain)

Domain for frequency schema

Default "general"
frequency_schema_idFrequency Schema Id (string) or Frequency Schema Id (null)(Frequency Schema Id)

Schema override

Any of:

Schema override

string(Frequency Schema Id)

Schema override

context_metadataContext Metadata (object) or Context Metadata (null)(Context Metadata)

Optional context metadata (createdAt, sourceType, etc.) to improve extraction.

Any of:

Optional context metadata (createdAt, sourceType, etc.) to improve extraction.

curl -i -X POST \
  https://memoryserver-staging-223473570766.us-west1.run.app/v1/holographic/metadata \
  -H 'Content-Type: application/json' \
  -H 'X-API-Key: YOUR_API_KEY_HERE' \
  -d '{
    "content": "string",
    "domain": "general",
    "frequency_schema_id": "string",
    "context_metadata": {}
  }'

Responses

Successful Response

Bodyapplication/json
statusstring(Status)
Default "success"
dataobject(MetadataData)required
data.​metadataobject(Metadata)required

LLM-extracted metadata keyed by frequency field name

data.​metadata.​property name*anyadditional property
data.​phasesArray of numbers(Phases)required

14 phase values for on-device transform

data.​domainstring(Domain)required
data.​frequency_schema_idstring(Frequency Schema Id)required
data.​timing_msnumber(Timing Ms)required
Response
application/json
{ "status": "success", "data": { "metadata": {}, "phases": [], "domain": "string", "frequency_schema_id": "string", "timing_ms": 0 } }

List available holographic domains

Request

Returns all available frequency schemas organized by domain. Use the schema_id or domain shortname in transform/rerank calls.

curl -i -X GET \
  https://memoryserver-staging-223473570766.us-west1.run.app/v1/holographic/domains \
  -H 'X-API-Key: YOUR_API_KEY_HERE'

Responses

Successful Response

Bodyapplication/json
statusstring(Status)
Default "success"
domainsArray of objects(Domains)required
domains[].​schema_idstring(Schema Id)required
domains[].​namestring(Name)required
domains[].​domainstring(Domain)required
domains[].​descriptionstring(Description)
Default ""
domains[].​num_frequenciesinteger(Num Frequencies)required
domains[].​is_customboolean(Is Custom)

True if created by developer via POST

Default false
totalinteger(Total)required
shortcutsobject(Shortcuts)

Shorthand aliases (e.g. 'cosqa' -> 'code_search:cosqa:2.0.0')

Response
application/json
{ "status": "success", "domains": [ {} ], "total": 0, "shortcuts": { "property1": "string", "property2": "string" } }

Create a custom frequency schema

Request

Define a custom frequency schema for your specific domain. Maps your metadata fields to the 14 standard brain-inspired frequency bands. Custom schemas are scoped to your API key.

Bodyapplication/jsonrequired
namestring(Name)required

Schema name in format 'company:domain:version' (e.g. 'acme:support_tickets:1.0.0')

Example: "acme:support_tickets:1.0.0"
descriptionDescription (string) or Description (null)(Description)

Human-readable description

Example: "Support ticket classification schema"
Any of:

Human-readable description

string(Description)

Human-readable description

fieldsArray of objects(Fields)[ 1 .. 14 ] itemsrequired

Frequency field definitions (1-14 fields, one per frequency band)

Example: [{"frequency":4,"name":"priority","type":"enum","values":["P0","P1","P2","P3"],"weight":0.9},{"frequency":6,"name":"component","type":"free_text","weight":0.7},{"frequency":12,"name":"resolution_type","type":"enum","values":["bug_fix","config","wontfix"],"weight":0.8}]
fields[].​frequencynumber(Frequency)required

Hz value (must be one of the 14 standard frequencies: 0.1, 0.5, 2.0, 4.0, 6.0, 10.0, 12.0, 18.0, 19.0, 24.0, 30.0, 40.0, 50.0, 70.0)

fields[].​namestring(Name)required

Field name (e.g. 'ticket_priority', 'component')

fields[].​typestring(FrequencyFieldType)required

Field type

Enum"enum""free_text""numeric""boolean""date""sequence""multi_value_text"
fields[].​valuesArray of Values (strings) or Values (null)(Values)

Allowed values for enum type

Any of:

Allowed values for enum type

fields[].​descriptionDescription (string) or Description (null)(Description)

Field description

Any of:

Field description

string(Description)

Field description

fields[].​weightnumber(Weight)[ 0 .. 1 ]

Importance weight

Default 1
curl -i -X POST \
  https://memoryserver-staging-223473570766.us-west1.run.app/v1/holographic/domains \
  -H 'Content-Type: application/json' \
  -H 'X-API-Key: YOUR_API_KEY_HERE' \
  -d '{
    "description": "Support ticket classification schema",
    "fields": [
      {
        "frequency": 4,
        "name": "priority",
        "type": "enum",
        "values": [
          "P0",
          "P1",
          "P2",
          "P3"
        ],
        "weight": 0.9
      },
      {
        "frequency": 6,
        "name": "component",
        "type": "free_text",
        "weight": 0.7
      },
      {
        "frequency": 12,
        "name": "resolution_type",
        "type": "enum",
        "values": [
          "bug_fix",
          "config",
          "wontfix"
        ],
        "weight": 0.8
      }
    ],
    "name": "acme:support_tickets:1.0.0"
  }'

Responses

Successful Response

Bodyapplication/json
statusstring(Status)
Default "success"
schema_idstring(Schema Id)required

Generated schema ID

domainstring(Domain)required
num_frequenciesinteger(Num Frequencies)required
Response
application/json
{ "status": "success", "schema_id": "string", "domain": "string", "num_frequencies": 0 }

Memory

Operations

Memory Status

Operations

User

Operations

Feedback

Operations

Schema Management

Operations

Messages

Operations

omo

Operations

Namespace

Operations

Frequency Schemas

Operations

Holographic Transform

Operations

Instance Configuration

Operations

AI Proxy

Operations

Sync

Operations

Telemetry

Operations

Document

Operations

GraphQL

Operations

Authentication

Operations