Documentation
Using BlindSight
BlindSight sells answers about a dataset, never the dataset itself. This guide covers buying an answer, reading the privacy receipt, publishing your own vault and calling the API from an agent. Everything runs on NEAR testnet.
Overview
There are two roles:
- Publishers upload a dataset into a sealed vault and set a price per question. The dataset is encrypted at rest and is never shown to buyers.
- Buyers (people or AI agents) pay that price in NEAR to ask one question and get an AI-written answer.
The model (DeepSeek V3.2) runs inside an attested Intel TDX enclave on NEAR AI Cloud. On every question BlindSight checks the enclave's attestation, encrypts the question to the enclave, and verifies the enclave's signature on the answer.
Getting started
- Get a NEAR testnet wallet, such as MyNearWallet or Meteor.
- Fund it from the NEAR testnet faucet. Testnet NEAR has no monetary value.
- Click Open Marketplace on the home page and connect your wallet. The marketplace opens once the wallet is connected.
Asking a question
- Find a vault in the Browse tab, or pick one directly in the Ask tab. Each vault shows its price per question.
- Type your question. Aggregate questions work best, for example “Which segment has the highest year-over-year growth?”
- Review the price breakdown (vault price plus the platform fee) and approve in your wallet. One approval signs both transfers.
- BlindSight confirms both transactions on chain, then runs the question in the enclave. The answer appears with a link to each transaction on NEARBlocks.
The first question on a freshly started server takes about 25–35 seconds because verifying Intel's attestation takes around 20 of them. Attestations are then reused for 10 minutes and answers take about 8–12 seconds.
If something fails after your payment is confirmed, you can retry with the same payment. You aren't charged twice.
The privacy receipt
Each answer carries a Verified private answer badge. Open Details to see what was checked for that specific answer:
| Check | What it means |
|---|---|
| Intel TDX | The gateway and model quotes verified against Intel's certificate chain, bound to a fresh one-time nonce so they can't be replayed. |
| Model & GPU | The model attestation and the NVIDIA GPU verdict. |
| Encrypted to enclave | The question was sent with Oblivious HTTP (RFC 9458) to a key signed by the attested gateway, so only the enclave could read it. |
| Signed answer | The enclave's ed25519 signature over the exact request and response bytes, checked against the attested key. |
| Fingerprints | SHA-256 hashes of the question and answer, and the enclave's signing key. |
Enclave verification and encryption are mandatory. If the enclave can't be verified or the encrypted channel fails, your question is never sent and you can retry with the same payment. The answer signature is checked after the answer arrives. If that check can't finish in time, you still get the answer, the badge reads Private processing instead, and the details show which checks passed.
Publishing a vault
- Open the Publish tab in the marketplace.
- Add a title (up to 80 characters), an optional description (up to 220) and one or more
.csv,.txtor.mdfiles. The combined dataset can be up to 500 KB. - Set a price per question and the account that should receive payments.
- Approve the one-time publishing fee. Once it confirms on chain, the dataset is encrypted with AES-256-GCM and stored in a private bucket. Only the title, description, price and account names are listed publicly.
Buyers pay the vault price directly to your payout account. There is no escrow and no withdrawal step.
Use synthetic or non-sensitive data. BlindSight's own server decrypts the dataset in memory to build the prompt, so you are trusting that server with it. See Limits.
Removing a vault
Vaults you published show an Unpublish button when your wallet is connected. Removing one asks your wallet to sign a one-time message (NEP-413, no transaction or fee). The server checks that signature against a full-access key on your account, then deletes both the listing and the encrypted file.
Prices and fees
| Item | Amount | Paid to |
|---|---|---|
| Question | Set by the publisher | The publisher's payout account (the treasury for sample vaults) |
| Platform fee, per question | 0.01 NEAR | BlindSight treasury |
| Publishing fee, one time | 0.05 NEAR | BlindSight treasury |
Sample vaults cost 0.1, 0.15 and 0.2 NEAR per question. Network gas is extra and very small.
API for agents
Any program with a NEAR testnet key can buy answers without a browser:
- Transfer the vault price to the vault's payout account, and the fee to the platform treasury.
POST /api/query-teewith both transaction hashes:
{
"query": "Which segment grew fastest?",
"txHash": "<vault price transfer>",
"feeTxHash": "<platform fee transfer>",
"payerAccountId": "buyer.testnet",
"vaultId": "q3-financial-market-demand"
}A successful response contains insight (the answer), receiptId, payment (the verified transfers) and privacy (the receipt fields: attested, encryptedToEnclave, responseSigned, TCB statuses, GPU verdict, nonce, signer key and hashes). Errors return { success: false, error, code } with a 4xx or 5xx status.
Other endpoints
GET /api/vaultslists published vaults (metadata only).POST /api/vaultspublishes a vault. It requires a verified publishing-fee transaction.DELETE /api/vaultsunpublishes a vault. It requires a NEP-413 signature from the publisher.POST /api/verify-paymentchecks a transfer on its own, without running a question.
The server verifies that each transfer is finalized and successful, was signed by the payer, went to the right receiver, covers the price, is under two hours old and hasn't been used before.
Limits
- BlindSight's server is not an enclave. The path from BlindSight to the model is attested, encrypted and signed, but the server decrypts published datasets in memory to build the prompt. Moving that step into a TEE is the next milestone.
- Testnet only, with no escrow contract. Transfers settle directly to recipients.
- Questions are limited to 2,000 characters, and about the first 32,000 characters of a dataset are given to the model.
- Anti-probing is a best-effort heuristic. Repeated, overlapping or extraction-style questions against one vault are rate-limited (20 per 10 minutes). This raises the cost of reconstructing a dataset but doesn't make it impossible.
- Replay protection and anti-probing are kept in memory per server instance.
Troubleshooting
The wallet window didn't open
Allow pop-ups for this site, then try again. MyNearWallet may redirect the whole page instead.
“Potential probing attack detected”
You hit the anti-probing limit for that vault. Wait about 10 minutes, and ask broader questions rather than many narrow variations of one.
The answer is taking a long time
The first question after the server starts includes about 20 seconds of enclave verification. Later questions are faster.
“The private AI enclave couldn't be verified”
BlindSight refuses to send your question unless it can go encrypted to a verified enclave. This usually clears up within a minute, because verification keeps running in the background. Try again with the same payment.
Payment went through but no answer
Ask again. Your confirmed payment is reused, so you won't be charged a second time. Both transactions are visible on NEARBlocks.
Still stuck? Email prosperlinho@gmail.com or open an issue on GitHub.