Semantic Similarity

Serving

Text and embedding similarity scoring: cosine match and dedupe decisions at fixed model precision. POST /v1/semantic with {text_a, text_b} and get a similarity score as one JSON object. Deterministic. Pay per request in USDC; no account, no API key.

Endpoint: POST https://agent.pocket.network/v1/semantic-similarity/v1/semantic
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/semantic-similarity/v1/semantic \
  -H 'content-type: application/json' \
  -d '{"text_a":"the cat sat","text_b":"a cat was sitting"}'

Example response

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

{
  "portal": {
    "provenance": "third-party-supplier",
    "serviceId": "semantic-similarity",
    "schemaCheck": "unchecked"
  },
  "data": {
    "text_a": "the cat sat",
    "text_b": "a cat was sitting",
    "similarity": 0.3333,
    "metric": "jaccard-token-v1",
    "threshold_note": ">=0.3 suggests same-topic (tune per use)",
    "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 Semantic Similarity accepts, and whether each reads or writes.
Method	Effect
`GET /v1/health`	read
`GET /v1/version`	read
`POST /v1/semantic`	read

Schemas

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

Request schema

{
  "type": "object",
  "description": "Two texts to compare.",
  "properties": {
    "text_a": {
      "type": "string",
      "description": "First text."
    },
    "text_b": {
      "type": "string",
      "description": "Second text."
    }
  },
  "required": [
    "text_a",
    "text_b"
  ]
}

Response schema

{
  "type": "object",
  "description": "For POST /v1/semantic, a JSON object with a `similarity` score. 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."
}