A machine cannot open a bank account. It can hold a wallet.

$SGHT is what this service charges in, so an agent that has never met its operator can still buy one answer. It is live. The rail is not charging yet — no wallet and no rate are set, so every tool below is still free. This page quotes no price, no supply and no return; the contract is the one fact about it worth publishing.

Contract — bonding curve 0x9288a2961368cCebF2E2509a877Eb8EE578857fc

Still on its bonding curve, so this address is replaced if it graduates. Check here before sending anything — this page and Virtuals are the only places it is published.

Why a token at all

An agent has no billing address. It cannot answer a 3-D Secure prompt, cannot open an account, and cannot agree to terms on anybody's behalf. Every one of those is load-bearing in card payments and none of them has a machine-shaped answer.

The workaround the industry settled on is to make the machine borrow a human's credentials: an API key, issued to a person, billed to a person's card, pasted into a program. It works, and it means every purchase a machine makes has to be arranged in advance by somebody who signed up first.

A wallet is the one payment instrument a machine can hold on its own terms. That is the whole of the argument, and it is the only claim this project makes for the token.

What is being sold

Status pages are current-state instruments. They carry a few months and then the incident is gone, and with it the record of how a provider actually behaves — which is the only thing anybody wanted from a status page in the first place. This archive has been keeping them: 850 outages across 22 providers, reaching back 730 days, each with the duration the provider itself announced.

Announced durations, median across incidents that published both a start and an end. A median is not a promise about the next one, and an incident never given an end time is not counted here.
Provider	Incidents	Median minutes
Twilio	199	342
Cloudflare	104	74
OpenAI	83	135
GitHub	71	81
Anthropic	68	67

Beside it: 468 release lines already past the date they stop receiving security fixes, 24 more inside the next window, and 415 models with every price change dated. None of that comes from a repository host, and none of it can be reconstructed later by anybody who did not start collecting when this did.

How a payment happens

The protocol is x402, HTTP's own answer to being asked for money. The server replies 402 with what it wants, the caller pays, and the caller asks again. There is no signup step because there is nowhere to sign up to.

Four messages. No account is created at any point, and none is needed.
→	POST	/api/mcp	An agent asks for one reading.
←	402	PAYMENT-REQUIRED	The price, the asset, the chain, and where to send it.
→	POST	PAYMENT-PAYLOAD	The same request again, carrying the receipt.
←	200	the reading	Verified on chain first, twelve confirmations.

The refusal is not a wall, it is an invoice. This is what the server sends, rendered here by the same function that answers a live request:

{
  "x402Version": 1,
  "accepts": [{
    "scheme":      "exact",
    "network":     "robinhood",
    "asset":       "0x… no contract yet",
    "payTo":       "0x… no wallet yet",
    "maxAmountRequired": "5000000000000000000",
    "resource":    "https://sighttrue.com/api/mcp#provider_incidents",
    "extensions":  { "chain": { "caip2": "eip155:4663" } }
  }]
}

The CAIP-2 identifier is published because network is a bare word. A caller that has never heard of this network can still address it correctly, and a transfer sent to the wrong chain does not come back.

What a credit costs

Priced by how hard the reading is to get, not by how valuable it might be to you — that second one is a guess about your business. Which band a tool sits in is a statement about the work behind the answer.

1 credit

Restates a public source

The answer exists somewhere public. What is being paid for is not having to go and get it, in a shape an agent can act on.

typosquat_checkChecked across every registry read here, not npm alone.
registry_healthA registry outage stops every deploy that depends on it, and no one keeps the record.
model_withdrawnA retired model breaks somebody’s product with no notice, and the catalogue simply stops listing it.

2 credits

Joins sources nobody joins

Two or three published records, held together. Each half is free to anybody; the join is the work, and nobody else is doing it.

withdrawn_but_installedThe gap between a publisher saying stop and the world stopping is a number nobody publishes, and it is a direct measure of how many projects have not noticed.
runtime_deadlinesPackages declare the runtime they need and endoflife.date knows when that runtime stopped getting fixes. The pair finds dependencies pinning you to an unsupported runtime.
who_can_publishBus factor counts who writes a project. Nothing counts who can ship it, and a package with one publisher is a supply-chain risk whatever its contributor count.

5 credits

Rests on the archive

Answerable only because the reading was taken and kept, every four hours, for as long as this has been running. It cannot be reconstructed later by anybody who did not start then.

provider_incidentsStatus pages delete their own history. The same component failing seven times in a year is a fact only an archive can state.
model_price_historyPrice tables carry no history. A rise is announced in a blog post and then invisible.
time_to_fixOSV publishes advisory dates and registries publish release dates. The interval between them is how long users were exposed, and nobody joins the two.

What stays free

9 of the 31 tools are free and stay free — everything needed to decide whether to install a dependency. A test reads the server's own dispatch table and fails the build if any of them acquires a price, which is a different kind of commitment from a sentence on a page, including this one.

check_before_installCall this before adding a dependency. Returns only the facts a reviewer would be annoyed to discover afterwards: whether the publisher has withdrawn the package, whether it runs scripts on the installing machine, whether its repository is archived, how many advisories are on record, whether the licence is source-available, and how long since it was actually published. Each fact carries the address of the body that published it. It does not say whether to install; it says what is on record.
check_packageRead the current standing of one open-source package: downloads with the window they cover, OpenSSF scorecard, advisory count, licence, whether the repository is archived, and when it was last pushed to.
check_stackRead a whole dependency list at once and report what is archived, what carries advisories, what has a source-available licence, and what has not been pushed to in a year. Use when reviewing a package.json, requirements.txt, Cargo.toml, composer.json or Gemfile.
search_repositoriesFind watched repositories whose name contains a string, with their current readings. Use it to discover what is covered before calling the other tools.
compare_repositoriesHold two watched repositories against each other across downloads, OpenSSF scorecard, advisories, forks, stars and findings on record. Compares only; it does not pick a winner.
find_modelFind language models by price and context window, from a catalogue read daily across sixty providers. Use this before choosing a model: prices move without announcement and training data is out of date on the day it ships.
check_eolCheck whether a runtime, database or framework release is still receiving security fixes, and what to move to. Covers about two dozen products read daily from endoflife.date.
check_providerRecorded incidents for a hosting or API provider over a window, kept after the provider’s own status page dropped them.
list_readingsList every reading this server can return, what each one measures, and which require a key. Call this first if unsure which tool answers a question.

The full catalogue, by what the tools are about. 22 are paid.
Group	Tools	Free	Paid
Before you install	6	6	0
AI models	3	1	2
Runtime and infrastructure	4	1	3
Providers	4	1	3
Supply chain	5	0	5
Vulnerability timing	2	0	2
Community	1	0	1
For agents	6	0	6

What it is not

The list a token page usually leaves out. Every line here is a limit enforced somewhere else on this site.

It is not access to the site.Every page, every bundle and every archive here is free to read and free to download, for anybody, holder or not. Nothing is behind the token and nothing is planned to be.
It is not a governance token.Holding it does not vote on the watchlist, the thresholds, or anything else. The watchlist changes by reviewed commit, in public, which is slower and more accountable than a poll.
It is not a claim on revenue.It is payment for a service, in the ordinary sense that a token is what the meter reads. No share of anything is attached to holding it.
There is nothing to connect a wallet to.This site has no wallet connection and will not get one. A contract address and a copy button is the whole of the interface, by rule.
It does not make the readings better.Paid tools are not more accurate than free ones. They are harder to produce. A paid answer carries the same limits as a free one and states them in the same words.

Checking this

None of the above needs to be taken on trust. One command reads the manifest in the current directory and reports what is on record, with no account and nothing uploaded:

npx sighttrue check

Every reading is committed to a public repository, timestamped and append-only, and the bundles behind this page are at /data/index.json. The free tools answer without payment today, over MCP or one GET. If a figure here is wrong, it is wrong against a file anybody can open — which is the only version of a claim this project is willing to make.