dev.aiseek/aiseek

Tools

• change_history

  How AiSeek's evidence record for one published change developed, and what AiSeek knew about it at an earlier moment. Always returns the change's receipts per claim, newest first (each names its parent receipt, so the revision chain reads from the list, with class, statuses and independence counts), and the change as it was when first published when the plan's window reaches that date. With `known_at` it also returns the change as known at that moment: whether readers could see it then, whether its headline wording changed later, and each claim's newest receipt written by then. Limits that are part of the answer: history is recorded from the day SeekTrace began, and before it a result says precision EXISTENCE_ONLY (whether a record existed, never what it said); old headline text is not kept, so `current` is today's version and the wording check says when it differs. `known_at` is limited by plan (Free 7 days back, Pro 30, Intelligence 90, Developer 180); asking further back is an error. A receipt records an assessment; it is not a certificate that a claim is true. Use it for what-did-we-know-then questions; use get_change for today's view. The id is the change id from latest_changes or search_changes. One call of the key's quota.

  shallow
• company

  Look up a company on AiSeek. The arguments choose the mode, and `slug` wins: with `slug` (the exact AiSeek company slug, e.g. toyota) it returns that company's profile (name, country, listings with ticker and exchange, description, recent published changes, stated claims, relations to other entities) and its page url, and `query` is ignored if also given. With only `query` (a name, alias or ticker) it returns {items}: up to 10 matching companies, most active first, each with its slug; call company again with a slug for the full profile. Financial filings are not included. Errors: an unknown slug; neither argument given. A description taken from Wikipedia carries its link (CC BY-SA 4.0). One call of the key's quota.

  shallow
• country_heat

  SeekEarth's Change Heat per country: how much verified change AiSeek recorded in each country, against the country's own recent normal. Heat runs from 0 to 100 and measures the amount of change, never danger or instability: 50 is an ordinary day for that country, 75 a day twice as busy. Each country also has delta against the day before, the number of changes, its domains, a convergence flag (three or more domains with important changes within 48 hours) and the heat of the last seven days. Use it to see where things are changing; use search_changes for the changes themselves. Without `country` it returns up to 60 countries, hottest first; with `country` (ISO 3166-1 alpha-2, e.g. JP) just that one. `domain` narrows to one coverage domain. `days` (1 to 90) is the window and is capped by the key's plan: Free 7 days, Pro 30, Intelligence and Developer 90; the answer says the window used and the plan's maximum. Changes with no single country are not in the list. One call of the key's quota.

  shallow
• earth_at

  SeekEarth for one place and one moment: what was happening there, from AiSeek's published changes and the Earth's layers. Give a place, either `country` (ISO 3166-1 alpha-2) or `lat` and `lon` with `radius_km` (default 500), and optionally a moment `at` (default now) and a window of `days` before it. `mode` NOW (the default) reads today's knowledge of those days and marks changes that became public only after `at` (knownAfter) or whose headline wording changed later; KNOWN reads what readers could see at `at`, and changes withdrawn since are only counted (withdrawnLater), never shown. Returns the place, the changes placed there (at most 30, most important first, each with its AiSeek url), the Change Heat of its countries on that day, and the items of the requested `layers` in force there (default: every event layer: disaster alerts, cyclones with forecast cones (not impact zones), tsunami messages, official weather warnings relayed as published, aftershock forecasts, conflict events, displacement, outbreaks, power plants, sanctions...), each with its layer's nature (OFFICIAL, AUTOMATIC estimate, FORECAST, OBSERVED) and the source to credit. Use it for where-and-when questions; use country_heat for heat across all countries, search_changes for changes by topic, change_history for one change's evidence over time. Limits by plan: `at` no further back than Free 7 days, Pro 30, Intelligence 90, Developer 180; `days` capped at Free 7, Pro 30, Intelligence 90, Developer 180 (the answer says the window used). One call of the key's quota.

  shallow
• get_change

  Get one published change with what AiSeek shows publicly about it: headline, summary, scores (importance, novelty, velocity, evidence strength), main subject, the languages it exists in, the id of its in-depth dossier when there is one, and its sources: for each outlet that reported it the name, the link, the publication date, the evidence level (PRIMARY, REGULATOR, COMPANY, INSTITUTIONAL, MEDIA, COMMUNITY, DERIVED) and its role. Quoted passages and source text are never returned, only names and links: open a source link, or the AiSeek page (url), to read them. Use it after latest_changes or search_changes. For the evidence receipts of the change and what AiSeek knew at an earlier time, use change_history. The id is the change id (a UUID); an unknown or unpublished id is an error. One call of the key's quota.

  shallow
• get_receipt

  Get one SeekTrace evidence receipt: the immutable record of how AiSeek assessed one claim and on what evidence. It carries the claim class (FACT, SUPPORTED or HYPOTHESIS), the assessment status (SUPPORTED, CONFLICTING, INSUFFICIENT_EVIDENCE or REFUTED), the currency status (CURRENT, STALE, SUPERSEDED, WITHDRAWN, UNKNOWN), the valid time, the evidence list (ids, source links, evidence level, stance, locators and content digests, never quoted text), independence counts (origins confirmed distinct, and origins not shown to be: unknown is never counted as independent), the parent receipt it revised and the sha256 digest of its canonical payload. A receipt records an assessment; it is not a certificate that a claim is true. Links to sources whose text may not be shown publicly are withheld (redactedEvidence counts them). Only public receipts can be read, on every plan; private research receipts never. Receipt ids come from change_history. To have the server recompute the digest use verify_receipt. One call of the key's quota.

  shallow
• latest_brief

  The latest brief: AiSeek's own summary of a period's changes, grouped by section, each item linking to its page. `type` DAILY (the default) covers one UTC day and comes out daily; WEEKLY covers a week and also carries the week's largest market moves, the events of the coming week and the judgments decided that week. On a Free key a brief opens one day after publication: a younger one comes back with only its title and summary, locked true, unlocksAt (when it opens) and no sections; paid plans read it at once. Use it for a digest; use latest_changes for the raw newest-first list. Returns the brief with its date, period, sections and url; an error if none has been published yet. One call of the key's quota.

  shallow
• latest_changes

  List the newest published changes on AiSeek (verified changes in the world: economy, markets, policy, technology, companies, science), newest first by detection time, 20 per page. Use it to see what is new or to browse; use search_changes instead when you are looking for a topic, company or country. Returns {items, hasMore, page}: each item has id, title, summary, detection time, scores and the url of its AiSeek page. Page 0 is the newest 20; hasMore says whether page + 1 exists, up to page 25. Pass an item's id to get_change for its sources, or to change_history for its evidence receipts. Read-only; counts as one call of the key's plan quota.

  shallow
• recent_corrections

  Public corrections about published content, newest first: changes taken down (reason EDITORIAL, READER_REPORT or RIGHTS_REQUEST) and changes or dossiers that are still published while evidence behind them was corrected and is under review or was resolved in the last 30 days (reason SOURCE_WITHDRAWN, SOURCE_CHANGED, EVIDENCE_INVALIDATED, CLAIM_RETRACTED or CONFIDENCE_LOWERED). Each item has an id, kind, time, reason category, state (UNDER_REVIEW or RESOLVED), the target id while it is public and a title where one may be shown. A correction flags what depends on the corrected evidence for review; nothing is withdrawn automatically. Only items inside the plan's window are listed (Free 7 days, Pro 30, Intelligence 90, Developer 180); windowDays says which. Use it to check whether something you read earlier was corrected. At most `limit` items (1 to 50, default 20). One call of the key's quota.

  shallow
• release_calendar

  Scheduled releases and decisions between two times: central-bank decisions and speeches, statistics-office releases, earnings, rule effective dates, comment deadlines, trade measures, filings due, meetings, votes and product launches (kind POLICY_DECISION, DATA_RELEASE, RULE_EFFECTIVE, COMMENT_DEADLINE, TRADE_MEASURE, FILING_DUE, EARNINGS, MEETING, VOTE, PRODUCT_LAUNCH, SPEECH). Each event has its title, scheduled time (ISO 8601, UTC), precision (EXACT time, DAY date only, or WINDOW span), status, source name and link, region, importance and, for tracked figures, the previous reading and, once out, the new one: never a forecast, and policy-rate figures are left out. Range: `from` defaults to one day ago and `to` to 31 days ahead, both ISO 8601 and read as instants (UTC if no offset is given), at most 400 days apart. Free keys see only yesterday, today and tomorrow (UTC) whatever range is asked; paid plans see the whole range. Use it for what is coming; use latest_changes for what has already happened. One call of the key's quota.

  shallow
• search_changes

  Search published changes by words (a company, a country, a subject, a name). Use it to find changes about something; use latest_changes to browse what is newest without a topic. Matching is on headlines and summaries and the result is ranked by relevance, best first, not by time: a query with Chinese or Japanese uses a CJK-aware index, a Latin query also matches word forms (rate finds rates), and when nothing ranks a plain substring match is tried. Returns {items}: at most `limit` cards (1 to 25, default 10), each with id, title, summary, time and url. Use get_change on an id for the sources. Read-only; one call of the key's quota.

  shallow
• verify_receipt

  Ask the server to recompute a receipt's digest from the stored record and report whether it still matches: ok, digestMatches, canonicalForm, columnsMatch, evidenceRowsMatch and a list of problems (DIGEST_MISMATCH, NOT_CANONICAL, COLUMN_MISMATCH:<field>, EVIDENCE_ROWS_MISMATCH, PAYLOAD_UNREADABLE). ok true means the stored record is unchanged since it was written. A receipt records an assessment; it is not a certificate that a claim is true. Use it after get_receipt, or before you cite a receipt. Public receipts only; an unknown or non-public id is an error. One call of the key's quota.

  shallow

Embed this server’s score

Tool count and median score across every tool in this server’s corpus — honest in a way a single cherry-picked tool’s badge wouldn’t be.

[![Vouch score](https://vouch.tools/api/servers/512b7307-2f1b-43a6-9207-f75a495dfbeb/badge.svg)](https://vouch.tools/servers/512b7307-2f1b-43a6-9207-f75a495dfbeb)