Text Embeddings

Serving

Open-weight text embeddings at a fixed model and precision: deterministic vectors for RAG and memory pipelines, identical across suppliers. POST /v1/text with {inputs} (a string or array of strings) and get the embedding vectors as one JSON object. Pay per request in USDC; no account, no API key.

Endpoint: POST https://agent.pocket.network/v1/text-embeddings/v1/text
Price per call: $0.005 USD
Networks payable on: Base (eip155:8453), Tempo (eip155:4217)
Protocol: rest

Calling it

The first call returns 402 Payment Required with the terms. Sign for those terms and retry the same request with the payment attached.

Example request

A real, working call — the request the service card verifies against.

curl -X POST https://agent.pocket.network/v1/text-embeddings/v1/text \
  -H 'content-type: application/json' \
  -d '{"inputs":"hello world"}'

Example response

The response this call returned, captured 2026-09-21 23:49:40 UTC.

{
  "portal": {
    "provenance": "third-party-supplier",
    "serviceId": "text-embeddings",
    "schemaCheck": "unchecked"
  },
  "data": {
    "embeddings": [
      [
        0,
        0,
        0
      ]
    ],
    "dim": 64,
    "count": 1,
    "method": "feature-hashing-v1 (md5, sign-hashed, l2-norm)",
    "note": "deterministic model-free embeddings: identical input+dim => identical vector on any supplier. NOT a neural model; declared honestly.",
    "deterministic": true,
    "as_of": "2026-09-21"
  }
}

Try it

Make one real paid call from your own wallet — about $0.005 on Base (eip155:8453). The wallet signs; nothing here holds a key. You'll see exactly what the service answers.

No browser wallet found. Install MetaMask, Rabby, or Coinbase Wallet to try a call here.

EndpointRequest body

Supported methods

Methods the registry lists for this service. The portal forwards any call as sent; the supplier decides what it answers, and a delivered answer is settled.

Methods Text Embeddings accepts, and whether each reads or writes.
Method	Effect
`GET /v1/health`	read
`GET /v1/version`	read
`POST /v1/text`	read

Schemas

Published by the service itself. The example above is generated from these.

Request schema

{
  "type": "object",
  "description": "Text to embed.",
  "properties": {
    "inputs": {
      "type": [
        "string",
        "array"
      ],
      "items": {
        "type": "string"
      },
      "description": "A single string or an array of strings to embed."
    }
  },
  "required": [
    "inputs"
  ]
}

Response schema

{
  "type": "object",
  "description": "For POST /v1/text, a JSON object with an `embeddings` array of fixed-length vectors. The exact shape is the service's own and is not pinned here; errors return a JSON object with an `error` field, and the GET routes return their own small JSON documents."
}