Search Result Reranking

Serving

Cross-encoder reranking of retrieved documents by relevance to a query, at fixed model precision. POST /v1/reranking with {query, documents} and get the reordered ranking as one JSON object. Deterministic. Pay per request in USDC; no account, no API key.

Endpoint: POST https://agent.pocket.network/v1/reranking/v1/reranking
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/reranking/v1/reranking \
  -H 'content-type: application/json' \
  -d '{"query":"cat","documents":["a cat sat","dogs bark"]}'

Example response

The response this call returned, captured 2026-09-21 23:48:57 UTC.

{
  "portal": {
    "provenance": "third-party-supplier",
    "serviceId": "reranking",
    "schemaCheck": "unchecked"
  },
  "data": {
    "query": "cat",
    "ranking": [
      {
        "index": 0,
        "score": 0.2761,
        "preview": "a cat sat"
      },
      {
        "index": 1,
        "score": 0,
        "preview": "dogs bark"
      }
    ],
    "scoring": "bm25-lite-v1 (term overlap + length norm)",
    "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 Search Result Reranking accepts, and whether each reads or writes.
Method	Effect
`GET /v1/health`	read
`GET /v1/version`	read
`POST /v1/reranking`	read

Schemas

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

Request schema

{
  "type": "object",
  "description": "A query and the documents to rerank.",
  "properties": {
    "query": {
      "type": "string",
      "description": "The query to rank against."
    },
    "documents": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "The candidate documents."
    }
  },
  "required": [
    "query",
    "documents"
  ]
}

Response schema

{
  "type": "object",
  "description": "For POST /v1/reranking, a JSON object with a `ranking` array ordered by relevance. 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."
}