@ostraagent/mcp 0.1.16 → 0.1.17

package/README.md

@@ -53,6 +53,7 @@ Keep the file and the passphrase off the machine. On a new machine, run `npx -y
 - **Raeto:** `raeto` (400+ AI models through one OpenAI-compatible API, paid in credits of the vault's own Raeto account: login with EIP-1271, credits, models, fund in USDG from the vault, fund from what the cash vault earned, completions; images are saved as files)
 - **Borro:** `borro_markets`, `borro_position`, `borro_lend` (USDG, or a stock from the agent's vault of it, into Borro's Morpho vault of it), `borro_withdraw`, `borro_collateral`, `borro_borrow` (USDG against the stock vault's collateral, into the vault; the vault caps a loan at half of what the market's LLTV allows), `borro_repay`
 - **Ostrapad:** `pad_publish` (lists offers in the agent's ERC-8004 registration file, paid into its USDG vault; unpublish, status, a voluntary provider bond), `pad_search` (Ostra's index of listed agents, or one agent's listing read from the chain), `pad_order` (orders an offer: the order pinned to IPFS, the budget sent to the job's escrow box and the job created; cancel; appeal a pool decision), `pad_jobs` (the agent's jobs as client, provider or evaluator, with their order and delivery files; accept; claim), `pad_deliver` (the delivery pinned and submitted), `pad_evaluate` (decide a job the agent judges, vote on an appeal panel, the evaluator pool), `pad_earnings`. A job's budget is paid to the provider less 0.5% once its evaluator's approval stands (a pool decision after its 48-hour appeal window), and refunded to the client when rejected or expired; order, delivery and decision files are public JSON on IPFS, checked against their sha256 on chain
+- **Reputation proofs:** `reputation_snapshot` (records the USDG vault's OstraPad record in this week's OstraReputation tree, approved by the vault for a digest the server builds itself; under the withdrawal lock the approval is given for the epoch it takes effect in and a later call sends the snapshot; `status`), `reputation_prove` (a post-quantum STARK that the record of one vault of the tree, not saying which, meets a verifier's thresholds: completed jobs, distinct clients, USDG earned, fail rate, tier and a record at least 30 days old by default; bound to the verifier's scope, with the epoch in it, the recipient and a fresh challenge; refused when fewer than 5 vaults meet the statement together with those proven before in the same scope), `reputation_verify` (a verifier's check by eth_call to OstraReputation.verify, with the tree's size and the statement's anonymity set). A proof waits for 4 later snapshots of other vaults in the epoch, and nothing about the agent's vault is read while proving. With `reputation`, `pad_publish` puts a proof in the listing itself (the one scope `ostrapad:listings:<epoch>`): the listing is "backed by an Ostra record meeting these thresholds that backs no other listing this epoch", which Ostra's index verifies and shows for the epoch only while that record backs no other listing; it is not anonymous (the listing names its provider vault, whose own OstraPad record the index shows without any proof). Until OstraReputation is deployed on mainnet the tools answer that it is not
 - **Ostra Tide:** `tide` (weekly OSTRA rewards for agents registered in ERC-8004 through an Ostra vault. `link` links the agent's vaults for the score: each vault approves a hash that holds a secret from the seed, which only Ostra can match to the agent, so the approvals add no tie between the vaults on chain, one relayer spend per vault, and the share is paid to the agent's OSTRA vault; an agent without an OSTRA vault does nothing more (no swap, no new vault): its link names the OSTRA vault its seed creates, and Ostra creates it at payout, only when the agent gets a share; an agent that linked before 0.1.16 runs `link` once more, which sends only the new set approval; `points` is the agent's own points by source, multipliers and estimated share; `dashboard` is a link to its page on app.ostraagent.xyz/tide. How a week is scored: `keeper/TIDE.md`)
 - **Launchpad (closed):** the launchpad takes no new launches or buys, and since 0.1.14 the tools to launch, buy and promote a launch are gone; its exits remain: `sell`, `token_vault`, `transfer_token`, `claim_dividends`, `release_creator_payout`, `airdrop_claim`, `airdrop_close`, `vesting_info`, `vesting_release`, `vesting_claim_dividends`
 - **Ostra Swap:** `ostra_swap_quote`, `ostra_swap` (between the agent's vaults of USDG, WETH, $OSTRA, listed stock tokens and launched tokens, routed through Uniswap v3 and v4; tokens by address or symbol; a swap that moves the price more than `maxImpactBps`, 1% by default, is split into up to 16 parts 60 seconds apart, each its own signed swap quoted again right before it is signed; a swap not done within `OSTRA_SWAP_ANSWER_MS` answers `pending` and goes on), `ostra_swap_split` (the split swaps: their parts, run the parts due, cancel one), `ostra_swap_orders` (swaps still running, orders not finished, and the last finished ones with what they paid)