Changelog

What changed in the API, the dashboard, the SDKs, the CLI and these docs, newest first.

2026-09-09

Dashboard

  • Playground results show the publisher alongside the journal and publication details, making sources easier to identify.
  • You can clear the playground's recent calls for your current organisation.
  • Legal documents open in a new tab during sign-in and setup, so checking a policy no longer takes you away from the form you are completing.

2026-09-08

API

  • Search filters out very short fragments, such as isolated headings, so results contain more useful text. See Search.

Dashboard

  • The playground's Code tab shows the request with the Python, TypeScript and Go SDKs, the same calls the guides use; cURL stays the raw request. Results is the first tab, and the results panel scrolls on its own. See SDKs.

2026-09-07

API

  • Agents can request a missing journal or publisher with the free request_journal MCP tool. Available to organisations with access to a collection.
  • open_access filters across a meta-collection: a collection that holds only open-access content answers the filter as a whole, and open_access: false excludes it with a filterWarnings entry. license is returned in result metadata but is not a filter. See Filtering.
  • Collection listings show exact prices only. A meta-collection whose members all cost the same shows one price rather than a range, and a price that cannot be resolved is reported as unavailable, never as $0.00. There are no more estimated per-query costs. See Collections.
  • Balance and charge amounts over MCP are reported at ledger precision, so a sub-cent charge no longer rounds to $0.00.
  • People who join through an organisation invite no longer get a separate personal workspace created alongside it.
  • Reliability fixes for assisted search and for retrieval connection errors.
  • X-Query-Cost is what the request was charged. For a billing-exempt organisation it carried an estimate, which read as a charge; it is now 0.000000 whenever nothing was charged (exempt, trial and sandbox modes), on the REST headers and in the MCP billing footer. See Rate limits and billing headers.
  • A search on a collection that no longer exists answers 404 COLLECTION_NOT_FOUND instead of 503 QDRANT_UNAVAILABLE.

Dashboard

  • Request a journal or publisher from Data Sources and see your organisation's submitted requests.
  • The playground is rebuilt around the request: pick a key, choose collections as chips, ask, and send. Results render as reading rows with title, journal, year, DOI and source link and the query terms marked, with the raw response, headers and the request as cURL, Python, TypeScript and Go a tab away. A ledger line shows status, latency, results, tokens, what was charged and the balance, read from the response itself.
  • Results render as markdown by default (headings, lists and tables in the chunk text), with a Plain text view that marks the query terms. The ledger line names the billing mode and says "no charge" for exempt, trial and sandbox requests.
  • With Include figures on, figures render as thumbnails that open full size with their caption. Figures that were not fetched keep their label, caption and link.
  • The documentation pages inside the dashboard are retired. Every old /docs link, in the dashboard and on the public site, redirects to the matching page on docs.redpine.ai. The playground moved to /org/{orgId}/playground and stays in the sidebar next to API Docs.
  • The billing transaction table shows a sub-cent charge as <$0.01 instead of $0.00.

Documentation

  • This changelog.
  • Filtering documents open_access across open-access collections and that license is not a filter; Collections documents when priceRange is null.
  • Each tool on an integration page has its own anchor, so links from the playground land on the tool.

2026-09-04

CLI

  • New redpine preview, redpine confirm (alias unlock) and redpine balance, so the free-preview-then-pay flow works from the terminal. See Preview and unlock.
  • Reads REDPINE_API_KEY and REDPINE_BASE_URL, the same names the SDKs use. CONNECT_API_KEY and CONNECT_SERVER_URL still work.
  • Output is the JSON envelope whenever stdout is not a terminal; --json and --pretty force either. This is what the README always said and it now holds.
  • A tool result flagged as an error renders as the error envelope with a non-zero exit, instead of success.
  • redpine update verifies the download against the release's checksums.txt. A newer release is a notice on stderr, no longer a block on every command.
  • whoami labels sandbox keys.

2026-09-03

SDKs are public

  • Official clients for Python, TypeScript and Go. TypeScript is on npm as @redpine-ai/sdk; Go via the module proxy.
  • The SDKs add preview() and unlock(), and get_results returns the preview shape with locked, tokens and cost per row. New typed errors for 402 (insufficient credits) and 410 (expired).
  • Every guide on this site now shows the SDK call next to the cURL request.

API

  • Preview and unlock: POST /api/v1/search/preview runs a search for free and returns teaser rows with a price per row; POST /api/v1/search/unlock pays for the rows you choose. GET /api/v1/search/results/{queryId} returns the same shape. Previews last 7 days, and over MCP a confirm can be retried.
  • Sandbox mode: sk_test_ keys return synthetic fixtures at no cost, on the same endpoints. Every response carries X-Billing-Mode.
  • Assisted search falls back to a second model provider when the first is unavailable.
  • MCP search results no longer expose the internal retrieval score. It was a per-collection number that could not be compared across collections.
  • last_updated_date is filterable on the editorial collections. It is the freshness signal there, since editorial articles are revised in place rather than republished. See Filtering.
  • Integrations such as media and aviation tools are enabled per organisation, off by default. Turn them on from the Data Sources page in the dashboard.
  • Organisations on a billing exemption no longer open every MCP session with a "No balance remaining" notice.
  • Every email the platform sends, including the sign-in code and receipts, is readable on a phone without zooming.

Dashboard

  • API Keys: create a sandbox key, badged so it cannot be mistaken for a live one.
  • Data Sources: switch integrations on or off for your organisation, and see whether each data source is granted directly, included with a bundle, or open access.
  • Publisher organisations get an editorial theme across the dashboard, with the publisher's logo in the masthead.

Documentation

  • SDK examples on every guide, and the quickstart installs a client instead of showing raw HTTP.
  • The language picker remembers your choice across pages, and always has a tab selected.
  • MCP: setup guides per client (Claude Code, Codex, Cursor, Claude Desktop, ChatGPT and others) and the search, preview and confirm tool surface.
  • Which search endpoint: a short decision guide between direct, preview and assisted search.
  • Integrations lists the tools available to your organisations when you are signed in.
  • The X-API-Key header is documented as an alternative to Authorization: Bearer. See Authentication.

2026-09-02

API

  • Searches across several collections are merged by a cross-encoder reranker rather than by rank alone. Before this, equal-length result lists tied rank for rank and the wrong collection took the top slot in most measured searches. Single-collection searches are unchanged.

2026-09-01

Documentation

  • This site, docs.redpine.ai, is live.
  • The API reference is generated from the public OpenAPI spec, the same spec the SDKs are built from.
  • /llms.txt and /llms-full.txt serve the docs as Markdown for agents, and any page is available as Markdown by appending .md to its URL.

API

  • Search results are cached reliably, including assisted search, so re-fetching by queryId within 7 days works every time.

2026-08-31

API

  • The organisation audit log lists only events that belong to your organisation. Actions taken by Redpine staff from outside the organisation are attributed to "Redpine Staff".
  • A meta-collection can bundle integrations alongside collections. Tools included this way appear on the Data Sources page and over MCP.
  • A signup through an invite link gets a welcome email that names the invite and what it grants, and lands back on the invite.

2026-08-28

API, Dashboard

  • An invite link can require accepting a terms document before it is claimed. The acceptance is recorded with the claim.
  • The post-signup setup commands for Claude Code and Codex are corrected. Both failed on first use before.

2026-08-27

API, Dashboard

  • isbn, open_access, chapter_number, chapter_title and chapter_authors are indexed filter fields on every collection, and article_type accepts book and book-chapter. See Filtering.
  • Invite links: an invite from Redpine is claimed at app.redpine.ai/redeem/{code}. It can grant credits, collections and integrations to the workspace you choose, and the page shows what it grants before you claim.
  • New accounts get a three-step onboarding on first visit: connect a client, see what you can reach, add a card for premium content. It can be closed and reopened.

2026-08-25

API

  • Search no longer expands query terms from a synonym dictionary by default. Measured on real queries, expansion lowered ranking quality. Where it still applies, an acronym expands only when written the way the dictionary spells it (PCR, not pcr), and a phrase matches only at word boundaries.
  • Over MCP, a search across a meta-collection names the source collection on each result, and the search-{collection} tool description lists the sources it covers.

Dashboard

  • A new visual design across the dashboard: surface hierarchy, rounded controls, one type family.
  • An integration's own error message is shown as a tool error in the playground, not as a malformed request.

2026-08-23

API

  • A tool that ran and returned a domain error (no results for that keyword, a rule that said no) now returns 422 TOOL_ERROR with the tool's message. It was reported as 502, which behind the CDN lost the message entirely.
  • Fixed intermittent 503 responses under bursts of MCP connection attempts.

2026-08-20

API

  • A paid MCP confirm returns doi, pmid, pmcid and url on every result that has them, so results can be cited. Editorial content, which has no DOI, is located by url.

2026-08-19

API, Dashboard

  • Search runs on a new multilingual embedding model with a normalised metadata schema: publication_date is a real date field, and article_type and section use controlled vocabularies. See Filtering.
  • When an MCP search fails, the error says why (a timeout while a large collection warms up, a connection failure) with an error_code, instead of a generic "please try again".
  • The public OpenAPI spec documents the billing response headers and the assisted-search semantics, and matches the live schemas.
  • Billing: one page for balance, adding funds, payment settings and a single activity table with payments and disputes. The old billing routes redirect.

CLI

  • redpine search takes --filter key=value (also !=, >=, comma-separated lists) and --filter-json for a full filter document.
  • Updated Go toolchain and dependencies.

2026-08-18

API

  • Fixed: POST /api/v1/search/assisted returned a validation error for a day, because the per-collection search route captured it.
  • Meta-collections support MCP preview and confirm, and a meta-collection can be open to every organisation.

2026-08-17

API

  • Meta-collections: a named collection that spans several publisher, journal or curated collections, searched and billed as one unit. GET /api/v1/search/collections lists a meta-collection with its member names, member count and price range; pass its name as collection to search every member together. See Collections.

2026-08-11

API, Dashboard

  • Articles listed as retracted are excluded from search results on the scholarly collections.
  • Signing out revokes the session on the server, not only in the browser.
  • MCP connections no longer count toward the organisation's API key limit, which had blocked key creation for organisations with many connected clients.
  • Invite or add several people in one submission: the members dialog takes a pasted list, and a bad address is reported beside the successes instead of failing the whole batch.
  • A missing display name is filled from Google on sign-in; otherwise the dashboard asks for one.
  • Error messages in the dashboard show the API's own message instead of a generic one.

2026-08-10

API, Dashboard

  • Collection names are matched case-insensitively, so any capitalisation of a name resolves to the same collection. Display spelling is unchanged.
  • Publisher dashboard for content partners: earnings, tokens served, citations, top content, a geography view, and a live feed of the last hundred citations of your content.
  • The organisation audit log records how each sign-in happened (Google, one-time code, passkey) and sign-ins refused by the identity provider.

2026-08-07

API

  • A revoked API key returns 401 API_KEY_REVOKED rather than INVALID_API_KEY. See Errors.
  • Every search result carries the name of the collection it came from.
Was this page helpful?

On this page