{"id":"org.aspern/aspern","slug":"org-aspern-aspern","title":"ASPERN: counterparty checks for agents","description":"What the chain records about an address before you pay it, and whether a payment fits it.","version":"1.3.0","publisher":{"kind":"domain","id":"aspern.org","label":"aspern.org","url":"https://aspern.org"},"website":"https://aspern.org","repository":"https://github.com/aspern-org/aspern-docs","remotes":[{"type":"streamable-http","url":"https://aspern.org/mcp"}],"packages":[],"published":"2026-11-04","updated":"2026-11-04","status":"online","auth":"","latency_ms":1217,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"identify","title":"Identify the party behind an identifier","description":"Call this FIRST whenever you hold something other than a wallet address. Give it a transaction hash, an http(s) URL, a hostname or an ERC-8004 registration number and it says which party that is, with the evidence for the link, so the other tools here can then be called with the address. It never picks between candidates: where a hostname or id matches several parties, `address` comes back null an","read_only":true},{"name":"check_service_endpoint","title":"Check a service endpoint before connecting","description":"Call this before connecting to a service. Give it the http(s) URL of an MCP or A2A endpoint and it says who declares it, whether our daily probe reached it, what it answered with, and how many of the last readings answered. It keeps three things apart and never merges them: what an identity DECLARES the endpoint offers, what a probe OBSERVED, and the readings behind that. Read `drift` where presen","read_only":true},{"name":"preflight_payment","title":"Weigh one payment before sending it","description":"Call this immediately before sending a payment, every time — not once per counterparty. It weighs THIS payment (the amount, the chain, the endpoint) against what the address has actually done: the price the seller themselves published for that endpoint, the address that endpoint names as its payee, the largest payment this address has ever received, and whether it has ever been paid on the chain y","read_only":true},{"name":"vault_assessment","title":"","description":"THE HASH-COMMITTED ASSESSMENT OF A VAULT, in the shape ERC-8004’s Reputation Registry points at, and the only thing here a third party can publish on chain under their own name. Until 2026-10-21 this document was reachable from the API and the web and from NO tool, so an agent could read every figure behind it and not the document itself. Each dimension is its own score and they are never blended:","read_only":true},{"name":"vault_exits","title":"What actually left a vault","description":"SEND `exitAmountUsd` WITH THE POSITION YOU ARE WEIGHING and this answers whether that size has ever cleared here: the schema has carried it since 2026-10-08, and an auditor still had to find it by guessing because this sentence did not say so. Without it the answer still describes the capacity; with it, `exitCapacity` says `covered-now`, `above-declared` or `unknown` for your amount, and whether a","read_only":true},{"name":"vault_risk_dimensions","title":"Six risks across every vault we score","description":"SIX RISKS, NOT ONE WORD, across every vault we score. A risk band is a weighted whole and a reader takes it as a summary of everything, which it is not: ours weighs drawdown, crowding, exit, concentration and consistency, and it contains NO reading of who may move the money. Two vaults read `low` while a multisig needing a single signature controlled them. So this groups what is already measured i","read_only":false},{"name":"portfolio_screen","title":"What the vaults you hold share","description":"READ THE VAULTS YOU HOLD TOGETHER. This one is about a SET rather than a single subject; an allocator does not hold one subject. This answers the three questions that only exist across holdings and that no vault page can show you: a CONTROLLER behind more than one of them, a MARKET behind more than one of them, and an EXIT that is not the sum of the exits. It is a screen, not advice: there is no a","read_only":true},{"name":"capital_coverage","title":"How much capital we can actually read","description":"BEFORE YOU TRUST ANY COVERAGE FIGURE FROM US, ask this. It says how much of the market each vault reading actually covers, counted TWO WAYS: by number of open vaults and by the capital in them. They differ by a lot, and the difference is the finding — more than half our vault COUNT is one venue’s small automated vaults, so a count-weighted coverage figure is mostly a statement about that venue and","read_only":true},{"name":"exit_lifecycle_coverage","title":"How much of the way out we can see","description":"HOW MUCH OF THE WAY OUT WE CAN SEE, phase by phase, across every open vault. Getting out has four phases — a request filed, something set aside to claim, money that actually left, and an attempt that failed — and we read THREE. The fourth is on this answer anyway, with its reason: no vault state records a redemption somebody attempted and could not complete, so reading it needs every transaction s","read_only":true},{"name":"endpoint_coverage","title":"How well we know whether declared endpoints answer","description":"BEFORE YOU TREAT ANY ENDPOINT AS RELIABLE, ask how well we know. There is no uptime number here and there will not be one, because the states mean different things and summing them produces a figure about nothing: a 402 is an x402 seller doing exactly what it advertises, a 401 or 403 is credentials WE do not hold, a 3xx is a move we chose not to follow, and a timeout describes OUR attempt rather t","read_only":true},{"name":"payment_evidence","title":"Settled, linked and delivered, across the rails","description":"BEFORE YOU QUOTE ANY FIGURE FOR AGENT COMMERCE, ask which of three it is. Every payment shown to be one, x402 and ACP, is split into three figures that NEST and are never added up (x402 counts only the `protocol`, `route` and `facilitator` tiers below; the authorised transfers with nothing to show they were x402 are in `notShownToBeX402`, never in the figures): `settled` (paid on-chain), of that `","read_only":true},{"name":"evidence_for","title":"Every edge we hold about one subject","description":"Everything we hold about one subject, as edges, each carrying where it came from. Use it when you need to explain a decision rather than just make one, or to see what is MISSING before you act. Every edge has `source`, `observedAt` (when the world was in that state), `asOf` (when we read it — a fresh read of a stale fact is not a fresh fact), a `confidence` that names what it is confident IN, its ","read_only":true},{"name":"evaluate_action","title":"Weigh one action against a named policy","description":"Call this when you are about to DO something and need one answer you can act on: pay an address, connect to an MCP server, call a tool, or put capital into a vault. The answer depends on the AMOUNT, the ACTION, the POLICY you name and how much we actually read — so the same address can be `allow` for $5 and `abstain` for $5,000. Four decisions. `allow` means nothing we could check objects, up to `","read_only":true},{"name":"evaluate_vault_decision","title":"Judge a vault decision before capital moves (paid)","description":"Call this before an agent moves capital into or out of a vault, with the decision it is about to make: the vault, the amount, the MANDATE it must stay inside and the CLAIMS the decision rests on. It is judged against our stored due-diligence snapshot of that vault, deterministically and without a model, and comes back with a `verdict`: `supported`, `conditional`, `human_review_required`, `insuffic","read_only":false},{"name":"simulate_withdrawal","title":"Try a withdrawal before making it (free up to $1,000)","description":"TRY ONE WITHDRAWAL FROM A VAULT BEFORE YOU MAKE IT. Runs the vault’s own withdraw(amount, holder, holder) by eth_call at the head block, as the holder you name or, if you name none, as its largest depositor: the contract executes and nothing is signed, sent or spent. Says whether it would have gone through, the revert reason where it would not (e.g. NotEnoughLiquidity, TransferReverted past a V2 v","read_only":false},{"name":"test_purchase","title":"Test purchase, without paying","description":"WALK THE WHOLE PURCHASE OF AN x402 ENDPOINT WITHOUT PAYING, in the order a buyer actually asks the questions, stopping at the first one that objects. All five are asked in one pass and in that order, so the walk stops where a buyer would stop. Five steps: is the endpoint there, what does it charge RIGHT NOW, does the seller’s own catalogue entry agree with what it just said, does the record say an","read_only":false},{"name":"knock_on_endpoint","title":"Knock on an endpoint, with your own payment","description":"KNOCK ON AN x402 ENDPOINT AND GET WHAT IT SERVED. `test_purchase` beside this walks a buy WITHOUT paying and stops at the quote; its own caveat has always said that only paying and reading the answer establishes what arrives, “which is the half that needs your own wallet”. This is that half, and it is the same capability the web and the plugin have. WITHOUT `payment` it reads the terms: `accepts` ","read_only":false},{"name":"endpoint_disagreements","title":"Endpoints that contradict their own listing","description":"WHICH ENDPOINTS CONTRADICT THEIR OWN LISTING: they ask to be paid at an address the catalogue entry they published does not name. The contradiction appears only when the live handshake and the published listing are held together: either half on its own looks ordinary, since a reachable endpoint and a stated payee are each unremarkable alone. A disagreement is between two statements by the SAME par","read_only":true},{"name":"list_x402_endpoints","title":"What this address sells","description":"WHICH ENDPOINTS A PAYEE SELLS, or which ones match some text. The sharpest check a payment can get is the endpoint being bought, and until this a caller had to know its URL by heart. Nearly every catalogued resource names a payee, and the catalogue holds tens of thousands of them. Every field is the SELLER’s own catalogue entry and never our reading of it, and a listing is not evidence that the en","read_only":true},{"name":"list_policies","title":"The policies a decision can be made under","description":"The policies evaluate_action can be run under, in full: every rule, its id and the sentence it checks. Published deliberately, including to the agents being evaluated — a rule nobody can read is a rule nobody can correct. Free.","read_only":true},{"name":"counterparty_check","title":"What the chain records about one address","description":"Before paying or hiring an agent: what the chain records about that address. `byNetwork` splits it network by network: x402 payments received (and their dollars, stablecoins at face value), ACP jobs and paid dollars, Olas tasks and registrations, per chain and never added across rails, because one address can settle on several networks at once. Independent payers (counterparties that paid it and w","read_only":true},{"name":"vault_sanctions_screening","title":"Sanctions list screening of a vault (paid)","description":"One vault against the OFAC SDN list: its contract roles and its direct holders where the holder list is complete, exact address matches only, with the list version and whether it is current. Paid ($0.01). States: EXACT_LISTED_ADDRESS_MATCH (a match of an identifier, for review, not a finding about who controls it), NO_EXACT_MATCH (bounded: the list is not exhaustive, so this never means no sanctio","read_only":false},{"name":"vault_due_diligence","title":"Due-diligence report for agents (paid)","description":"The due-diligence report on one vault, cut to what an agent acts on: overallAssessment (published, conditional or withheld; publishedBand is null when withheld and partialBand is never the verdict), findings above the band, each risk dimension, capital and withdrawal bounds, metricStatus (each input current, indicative, stale, unavailable or not-read, with its times and expiry), completeness, warn","read_only":false},{"name":"vault_drift","title":"What changed on a vault (paid)","description":"What changed on one vault, day by day, between the stored daily due-diligence reports: the overall assessment (including when it became withheld or published again), each risk dimension, the withdrawable share, capital, control roles and the timelock, and the tested withdrawal. Paid ($0.01). A change can be the vault, what we could read, or our model; days with no stored report are listed under `g","read_only":false},{"name":"counterparty_evidence","title":"Evidence on a counterparty before trading (paid)","description":"Before trading with an agent or service: what the records actually say about it, in one answer. Identity links with their strength (declared by the agent, observed by us, or corroborated by a second party), settled payment history with first and last payment, active months and long silences, counterparties with top-1 and top-3 share, Herfindahl and repeat ratio, each catalogued service with its pr","read_only":false},{"name":"vault_check","title":"What the record shows about one vault","description":"Before putting capital into a vault: what the record shows about it. The headline is what a holder ACTUALLY EARNED set against the advertised rate, with the risk band, the components that apply, who runs it, and `keys`: who can move the money. Read `keys.actsAlone` before any return figure, because a strategy can be excellent and one private key away from being emptied; across what we read on 6 Oc","read_only":true},{"name":"find_vaults","title":"Find a vault by what it has done","description":"Find a vault by what it has DONE rather than what it is called. Free. The filter worth knowing is `earned`: `short` returns the vaults where a holder earned LESS than the venue advertises — how many there are is in the answer, never here — and `beating` the ones where they earned more. It matches on the same verdict vault_check leads with, `delivery.verdict`, over a comparable period (each row car","read_only":true},{"name":"operator_check","title":"Who runs the money, and how much is theirs","description":"The question that follows vault_check: who runs the money, and how much of it is their own. Free. Read `ownShare` with its limits, which travel inside it: the leader’s holding is readable on Hyperliquid and Drift ONLY, so elsewhere it is ABSENT and not zero, the median describes the strategies we can read rather than the manager, and a large own-share is evidence of alignment and never proof, beca","read_only":true},{"name":"list_vaults","title":"Find the vault you mean","description":"The vaults we read, so a caller holding a name rather than a slug can find the one it means. Free. Absence from this list means we do not read that vault, never that it does not exist.","read_only":true},{"name":"find_agents","title":"Find agents by what the record shows","description":"Find PAID ON-CHAIN SERVICES (an x402 seller, an ACP or Olas worker, a Masumi agent) by what the chain records rather than what they claim. MOST ARE NOT SHOWN TO BE AI AGENTS: every row is a paid on-chain service, and `subject.serviceKind` says only what the evidence shows (marketplace_worker, protocol_service, unknown_paid_endpoint; an AI decision is never recorded on these rails). Filters: filter","read_only":true},{"name":"counterparty_history","title":"One agent’s record day by day (paid)","description":"How one agent’s record has moved: dealings, independent payers, concentration and delivery, day by day. PAID, one cent a call over x402 — the median price of this rail. Without payment the tool answers with the price and how to pay it, and the free check remains available. The history begins the day we started keeping it; it is a record we keep, not one the chain gives away. WHY readOnlyHint IS fa","read_only":false},{"name":"stock_peg","title":"Does a tokenized stock hold its share price (paid)","description":"Does each token of one share hold that share’s price? Per token: the share on its exchange times the shares the token stands for, against the issuer’s reference and the deepest DEX pool, with the gap now and over the last seven days (worst gap, hours out of band while the exchange was open). PAID, one cent a call over x402; a question that matches no share is refused before any payment. A gap whil","read_only":false},{"name":"vaults_earned","title":"What depositors kept, against what was advertised","description":"What depositors actually KEPT, against what their vault advertised. READ `population` BEFORE QUOTING ANY SHARE FROM THIS. The comparison covers only the vaults where we hold BOTH an advertised rate and a realised one, which is a narrow and lopsided set, usually dominated by one venue: `population.largestVenue` names it and `population.concentration` says how much of the set it is. A share from her","read_only":true},{"name":"agent_changes","title":"What moved in the agent record","description":"What moved in the agent record, across every agent, since a date. The counterparty check answers what is true about one address NOW; this answers what changed, for all of them, which is the question anybody holding a list asks next. One row per FIELD that moved, not per address: an agent whose dealings and concentration both moved is two facts, and folding them would make you diff the answer to wo","read_only":true},{"name":"counterparty_bulk","title":"Check up to fifty addresses in one call (paid)","description":"Check up to fifty addresses in one call, each with its observations, AND what the set shares underneath: the parties that two or more of them pay. That second part is the one answer no per-address row can contain, because the input is your own shortlist — four agents stopping together because they all pay one party is invisible in four separate clean records. PAID two ways and they buy different t","read_only":false},{"name":"agent_dependencies","title":"What several agents rest on at once (paid)","description":"If your firm relies on several external agents, what do they rest on AT ONCE? Give it two to twenty-five addresses and it finds the parties more than one of them pays. THE PRODUCT IS THE DISTINCTION, NOT THE JOIN: finding that three agents paid the same address tells you almost nothing — on our rails one address is paid by 71 agents across 4,100 payments and another by three agents once each, and ","read_only":false},{"name":"agent_business","title":"Does this agent have a business (paid)","description":"Does this agent have a BUSINESS, and can any of it be demonstrated? Six questions an investor, a marketplace or an operator actually asks, each answered separately: are the addresses paying it really independent customers; is revenue growing or shrinking; how much is repeat custom; how many of those payments can be shown to have bought anything; what does it cost to run and to whom; and if it has ","read_only":false},{"name":"agent_economic_profile","title":"Agent economic profile (paid)","description":"One agent, four readings, in the order a buyer actually asks them: what it EARNS and from whom, whether its contracted work FINISHED and who signed it off, who it RESTS ON as a supplier, and whether it is still TRADING and its endpoints answer. Those questions are answered singly elsewhere on this server; this is the one that answers them together, over the same nightly record, so the four cannot ","read_only":false},{"name":"exit_screen","title":"Where has a size like mine actually cleared (paid)","description":"YOU HAVE A SIZE AND YOU WANT TO KNOW WHERE IT HAS ACTUALLY CLEARED. Every other exit reading here is about one vault; this asks the same question across every vault whose withdrawal history we have read, which is the question an allocator with capital actually has. Send `amountUsd` and each vault comes back with one of THREE verdicts, and the middle one is the finding: `paid-in-one` means a single","read_only":false},{"name":"vault_exit_confidence","title":"Could you get your money back out (paid)","description":"Before you put capital in, ask what evidence there is that you could get a PARTICULAR amount back out. Every other reading about a vault is about return or about risk of loss; this is about the practical question a holder has, and it is always about a size: \"can I get out\" has no answer, \"can I get $2m out of a vault with $400k free and 25,941 settled withdrawals behind it\" has several. Six readin","read_only":false},{"name":"check_action","title":"One check before you sign (paid)","description":"CALL THIS BEFORE YOUR AGENT SIGNS ANYTHING THAT MOVES MONEY. One request instead of five: it reads the counterparty record, decodes the calldata you are about to sign, looks up the seller’s own catalogue listing, runs an unpaid 402 handshake with the endpoint, and applies a published policy — and then, which is the point, compares them WITH EACH OTHER. The losses an agent actually suffers live bet","read_only":false},{"name":"inspect_payment","title":"Read the transaction you are about to sign","description":"Call this with the CALLDATA you are about to sign, before you sign it. Every other check here asks whether an address is worth dealing with; this asks whether the transaction is the one you think it is, and the two catch different losses. No amount of reputation makes the recipient in the bytes match the recipient on your screen, and a spotless counterparty record says nothing about an UNLIMITED A","read_only":false},{"name":"record_receipt","title":"Record what you did, so it can be checked later","description":"Call this AFTER you have paid an address or called a tool, to put what you did on the record. Until now this platform answered \"should I\" and never heard what happened, which is the difference between a lookup and a control layer: a receipt lets the next question about this subject be asked against a record instead of a guess, and lets a verdict we gave be read back against what followed. `referen","read_only":false},{"name":"receipt_status","title":"What became of a receipt you recorded","description":"What became of a receipt you recorded with `record_receipt`. We do not take a receipt on your word: each one is read against the payments WE read from the chain and judged `verified` (it paid the subject and the amount agrees), `contradicted` (which of the two did not), `not-found` (absent from what we read two days after it was filed, a statement about our reading and never that it did not happen","read_only":true},{"name":"monitor_subject","title":"Be told when the answer about an address changes","description":"Ask to be told when the answer about an address CHANGES. The dimensions are the ones the counterparty check already answers, so this is that same reading on a schedule rather than a second opinion; what it adds is the comparison. The first run records a reading and reports nothing — there is nothing yet to compare against, and a first reading dressed up as news is the thing this avoids. Idempotent","read_only":false},{"name":"vault_exposure_graph","title":"Where one vault is exposed","description":"Where one vault’s capital is exposed, as a graph: vault → market → collateral, loan asset and oracle. Every edge carries its size in dollars, its share of what the vault allocates, the vault’s share of the market, the LLTV where it secures, when it was read and where from. Cut from the vault’s due-diligence document, the same engine the report and vault_check use, so it says nothing the report doe","read_only":true},{"name":"agent_dd_report","title":"Due diligence on an ACP provider","description":"Due diligence on an ACP provider before hiring it: does it finish the work, who said the work was done, who pays it, is the record current, who is behind it, is it on a sanctions list. Each answer has a status and what would settle it. No score and never a statement that the agent is safe. `applies` is false for an address with no paid ACP job and judged completion, and that is not a finding about","read_only":true},{"name":"agent_hire_check","title":"Four questions before the first payment to an agent","description":"Before the first payment to an agent over x402: does its endpoint answer, does it charge what it lists, who pays it, does it deliver. Each answer is ok, caution or not_established, with what would settle it. x402 records a payment and nothing about delivery, so delivery stays not established there. `no_warning_found` is not a statement that the agent is safe to hire.","read_only":true},{"name":"compare_vaults","title":"Two to five vaults side by side, from each one’s report","description":"Compare 2 to 5 named vaults side by side on one taxonomy: identity (chain, address, platform, curator, operator), capital (reported assets, the venue’s withdrawable figure, the withdrawable share, and what the capital figure means, e.g. a book value whose recovery is not established), the assessment (status, published band, highest finding, findings above the band, critical flags) and the earned v","read_only":true},{"name":"compare_agents","title":"Two to five agents side by side, from each one’s record","description":"Compare 2 to 5 agent addresses side by side on one taxonomy, from the record we keep for every paid address: identity (registered name, ERC-8004 registrations, rails, chains), custom (counterparties, independent payers who were never paid back, payers it also paid, the largest payer’s share, the share who came back), money (received and paid out where priced, x402 payments), work (ACP jobs, comple","read_only":true},{"name":"find_stocks","title":"Tokenized stocks across issuers and networks","description":"Tokenized stocks on chain, one row per company across every issuer and network we read (Coinbase on Base; Robinhood on Robinhood Chain; xStocks on Solana, Ethereum, Arbitrum, BNB Chain, TON, Tron and others; Ondo on Ethereum, BNB Chain, Solana, HyperEVM and Robinhood Chain; bStocks (Binance) on BNB Chain; Dinari on Arbitrum, Ethereum and Base). A question resolves to the underlying first (ISIN, to","read_only":true},{"name":"stock_agent_activity","title":"Agents moving a tokenized stock, over a window","description":"How many AI agents moved a tokenized stock over a window you choose (default the last 24 hours): distinct agent addresses, transfers in and out, value at the issuer’s reference, by token and network. Ask by ticker (TSLA), company name (Tesla) or ISIN, or leave it empty for every stock. Free. Agents are the addresses we hold as ERC-8004 owners, ACP providers and clients, Olas task agents and x402 p","read_only":true},{"name":"vault_rwa","title":"A vault’s tokenized stocks and stablecoins","description":"What one vault holds in real-world assets: tokenized stocks it holds at its own address, what it has lent against tokenized stocks as collateral (exposure through borrowers, not stocks it owns), and whether its own asset is a stablecoin. Free. Holdings come from the registers we rebuild for the largest stock tokens; anything outside them is not seen, not absent.","read_only":true},{"name":"stablecoin_payments","title":"Agent stablecoin payments, over a window","description":"Agent payments in stablecoins over a window you choose (default the last 24 hours): how many x402 payments, from how many paying addresses to how many receiving ones, by token and network. Filter by stablecoin (USDC) or network. Free. Counts only payments shown to be x402.","read_only":true},{"name":"stock_agent_transfers","title":"Agent transfers of tokenized stocks (paid)","description":"Every transfer of a tokenized stock that touched an agent address over a window: the agent and its roles, the token, in or out, the amount and its value, the time and the transaction, newest first (up to 5,000). PAID per call, $0.10 over x402 (USDC on Base) or with a plan; the counts are free in stock_agent_activity.","read_only":false},{"name":"stock_holders","title":"Every holder of a tokenized stock (paid)","description":"Every holder of one tokenized stock, from the register rebuilt from its transfers since deployment: balance, value at the issuer’s reference, share outside the issuer’s own wallets, and transfer counts, largest first (up to 2,000). PAID per call, $0.10 over x402 (USDC on Base) or with a plan; concentration and the largest holders are free in stock_check.","read_only":false},{"name":"stock_issuer_check","title":"One tokenized-stock issuer: what, where, who controls it, OFAC","description":"One issuer of tokenized stocks (coinbase, robinhood, xstocks, ondo, bstocks, dinari): the entity and jurisdiction as its documents name them, what it has tokenized (tokens, companies, value at its reference values), on which networks, the control addresses its contracts answer (owner, minter, burner, pauser, sanctions list, registry; Solana mint, freeze and pause authorities and any permanent dele","read_only":true},{"name":"stock_buy_check","title":"Check a tokenized stock before you buy","description":"Check a tokenized stock BEFORE BUYING it, by its contract (or Solana mint) and network: can it be moved today (pause state, a permanent delegate), is a controlling address on the OFAC SDN list, does the pool price track the issuer’s reference, is there DEX liquidity to sell into, is it concentrated in one holder, and is it backed where the issuer reports reserves. Each question has a state (ok, ca","read_only":true},{"name":"compare_stock_tokens","title":"Compare one company’s tokenized stocks","description":"One company’s tokenized stock SIDE BY SIDE across issuers and networks, by ticker, company name or ISIN: supply, value at the issuer’s reference, pool premium, DEX liquidity, pause state, holders and the largest holder, reserves where reported, and each token’s buy-check status with its cautions. Each row is a different wrapper with its own controls. Free.","read_only":true},{"name":"stock_check","title":"One tokenized stock, every network it is on","description":"One tokenized stock by its contract address (EVM) or mint (Solana): the issuer, the network, supply (read on chain except Coinbase’s), the issuer’s reference value with its source and time, what is in issue in dollars, who controls the token where read (pause state, transfer policies, supply cap, roles), where it trades and at what premium to the reference (DexScreener, named), what is not yet rea","read_only":true}],"server_info":{"name":"aspern","title":"ASPERN — counterparty checks for agents","version":"1.3.0","websiteUrl":"https://aspern.org/connect"},"category":"finance","tags":["agents","crypto","analytics"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-09-24","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/org-aspern-aspern/"}