NEAR HACKATHON · Agent Economy

Thesis Agent

Take a thesis or claim, break it into parts you can actually check, and build a test plan for each part. No verdict is given for you. You add the evidence, then you mark each part yourself.

Built by Cryptoearn Gives, solo. The core thesis tool runs in your browser, signs nothing, and moves no money. Live quote, link check, and testnet proof panel send only the requests you trigger, described below.

Your plan is saved in this browser only (localStorage, no server) so a refresh keeps it. Clear saved plan removes it.

Step 3: How an agent would be paid for this work

DEMO DESIGN ONLY, not a live NEAR payment. In a full version, a checker agent would be hired for one sub-claim at a time, and paid only after it records a named, dated, openable evidence link. The job list below is that loop as a labelled demo: demo quotes, one counter-offer per job, a do-vs-buy line, and a receipt per job in the download. Nothing here is bought, hired, or quoted by a real agent. Separately, that payment rule IS proven on testnet by the escrow contract in the repository (contract/, thesis-agent-escrow2.testnet, testnet only) — but this page itself has no wallet and moves no money, and the live quote button below is dry-only, not a payment.

The agent may not exceed this cap. If the job list costs more than the cap, the extra jobs stay blocked until you raise the cap or cut the scope. This is the spending guardrail: an agent with a wallet, but with limits you set. Enter a whole number of demo units, 0 or more; an invalid cap is shown as an error and the previous cap is kept, never silently replaced.

Break a thesis down first, and the agent job list will appear here.

See near-integration.js for the exact code path. A real NEAR Intents call would need the user's own testnet account and approval, and is not part of this demo.

SEPARATE DEMONSTRATION, not a record of the demo jobs above: this button queries the NEAR testnet RPC for the escrow v2 contract with payer-only release control, v2.thesis-agent-escrow2.testnet, jobs job-v2-1 and job-v2-2. It signs nothing, moves no money, and needs no wallet. Reading blockchain records does not initiate or authorise a payment, and no demo job above has an actual escrow record unless that relationship is genuinely established. If the network or RPC is unavailable, this panel shows that fallback and the thesis tool above still works. Testnet only, free testnet NEAR only.

Live quote example, quote-only: 1 USDC on Arbitrum to USDC on Solana, requested with dry: true from the NEAR Intents 1Click API. The recipient is the example label "thesis-agent-demo.near" (Intents type), not a real wallet, and no funds are sent to it. If the live call fails or is blocked in this browser, the demo shows the local dry-run object instead and says so, rather than faking a quote value. A dry quote is not a payment, and no deposit address is ever issued here.

Why NEAR, and not just any chain

The reason it fits NEAR is specific: a checker agent may live on one chain and be paid from another, and NEAR Intents are built for exactly that kind of cross-chain intent, stated once and settled where the work happens, without the user bridging wallets by hand. The spending cap above is the other half: an agent that can spend, but only inside limits the user sets, and only released when evidence is recorded. That is the Agent Economy idea in one sentence: hire an agent for a verifiable job, pay it only for that job, and never hand it the keys to everything.

Two real, limited NEAR proofs now exist alongside this page, and are documented in README.md and HACKATHON.md: a dry-only live Intents quote (the button in Step 3, no payment, no deposit address) and a testnet escrow contract (thesis-agent-escrow2.testnet, testnet only, with real testnet release and refund transactions). This page itself still has no wallet and moves no money.

If those proofs did not exist, this would still be a working thesis-testing tool. The NEAR part is the reason it would scale as an agent market, not the reason the demo opens.

Try it yourself

  1. Type a thesis, then press "Break it down", then see a structured list of checkable parts.
  2. For each part, add an evidence note that names a source, gives a date, and gives a link or document name, then change its status from "Not yet tested", then see the progress bar move. A decided status is blocked until the note passes that check, and the missing element is shown by name.
  3. Press "Copy test plan as text" or "Download test plan (.md)", then see the full plan, with your notes included, plus a per-job receipt for every agent job (demo only).
  4. In Step 3, see one job row per sub-claim with its demo quote, do-vs-buy line, one counter-offer when the quote is above plan, and whether it is allowed, blocked by the cap, or cut. Cut a job and see the totals change; the download then records that cut in its receipt.

Full details, including what is real and what is demo only, are in README.md and HACKATHON.md.