inflectiv.ai valid

Inflectiv

Inflectiv turns unstructured information into structured datasets that AI

For agents: Inflectiv turns unstructured information into structured living datasets for AI, with an MCP server (27 tools), use cases, FAQs and a token economy.

structured-datasetsmcp-serverliving-datasetsai-datainai-token

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T04:59:10.083Z. Cached copy · Source on inflectiv.ai

# Inflectiv

> Inflectiv turns unstructured information into structured datasets that AI
> agents query directly, over API, SDK or MCP. The agent pays per question, the
> owner sets the terms, and agents can write back what they learn — so a dataset
> improves while it is being used instead of going stale the moment it ships.

Written for AI systems reading this site. Everything below is present tense
because it has shipped; anything still to come is marked as such.


## How an agent reaches a dataset

- MCP: twenty-seven tools over the Model Context Protocol. The server has been
  live since April and is reachable from five clients, including Claude and
  Cursor. One line to connect, no connector to build.
- API and SDK: authenticate, satisfy the dataset's access policy, and query it
  inside the reasoning loop. Ask for a cited answer and you get the records
  behind it — each with its source, its date and a similarity score. Ask for the
  ranked records alone and nothing is generated, so you can ground your own model.
- Write-back: with attachment mode on, an agent adds what it learned back into
  the dataset as it works.
- Instructions: every dataset carries a 5,000-character instruction field that
  lands in the prompt of every agent attached to it.


## What a question costs

- One credit per question. Not per row, per result, per content type or per
  effort tier. Asking for ranked records costs the same as asking for an answer.
- Every query carries a score threshold. If nothing clears it, you get nothing
  back and you are not billed.
- Credits come with a plan or as a top-up, and there is a free tier.
- When credits run out an agent settles in USDC over x402 on Base and carries
  on — no card, no invoice, no human approving anything.


## How a dataset is built and held

- Ingest files, URLs, documents, research or typed-in knowledge; Inflectiv
  structures it into records, embedding and de-duplicating as they land.
- Records are encrypted with Seal, the access policy is held on chain, and the
  data is stored on Walrus.
- The owner sets the terms: public or private, free or paid, and who may write.
- Datasets and records are written on Base or Sui.


## The economy

- $INAI is the settlement layer, not a consumer utility token. Fixed supply of
  16 billion, with no emissions tied to activity, usage or participation.
- A dataset may optionally launch its own token. That token is a market
  hypothesis about the dataset's usefulness. It is NOT an access key: holding
  one does not gate APIs, unlock features or substitute for credits.
- Creators earn two ways only: access fees they set, and appreciation of tokens
  they retained. There are deliberately no per-query royalties.
- Paid usage triggers protocol-level buybacks that burn the dataset token. Only
  paid SDK usage counts, so usage cannot be inflated to extract value.
- Proof of Knowledge and DataLabs are the model that extends this: domain
  economies competing each epoch for a known
…

Related sites

Other listed sites in AI and machine learning. See the whole category →

Machine-readable: GET /v1/resolve?q=inflectiv.ai · GET /v1/domain/inflectiv.ai · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for inflectiv.ai:
1. POST https://agentwebmap.com/v1/sites/inflectiv.ai/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://inflectiv.ai/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/inflectiv.ai/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/inflectiv.ai).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.