Skip to content
FurniOps

Product updates

Changelog

What is new in FurniOps, newest first: each capability the day it shipped, with the docs that explain it. Every API release, field by field, is in the API changelog.

API changelogAtom feed

The MCP server

  • MCP
  • AI

Connect Claude, ChatGPT, Cursor or any MCP client to your catalogue. Every tool is a public API route, so the same permissions, plan, rate limits and request logs apply.

  • Streamable HTTP at mcp.furniops.com/mcp, signed in with OAuth 2.1 and PKCE, or with an API key made for an AI agent
  • Consent is always asked: no MCP client is trusted by default
  • Write tools only for people's own tokens and agent keys, carrying ETags and idempotency keys
  • Limits per caller, and one metered call per tool call

AI agents that propose, and prove it

  • AI
  • Sources

Four agents now watch your catalogue: they file products into categories, repair a mapping when a vendor's file changes, onboard a new source from a probe, and explain what went wrong in a run.

  • Agents propose; they never write master data. Each proposal is checked against recorded data first
  • Set each agent's autonomy and daily budget, and see how often its proposals matched what people decided
  • Every model call is metered and budgeted per organisation

Your own OAuth apps, and 31 days of request logs

  • Identity
  • API

Register OAuth apps for your organisation, and read every API request your keys, apps and members made, kept for 31 days.

  • Web, single-page, native and machine apps, with secret rotation and an overlap window
  • Request logs show method, path, status, duration, caller and request ID; bodies are never logged

Source probes

  • Sources

Give FurniOps a vendor's website and it reports how to read it: the platform, any feed, sitemaps, structured data coverage and what robots.txt allows.

  • The onboarding agent turns a probe into a proposed source
  • Probes honour robots.txt and identify themselves

Bulk exports, usage and quotas

  • API
  • Platform

Export the whole catalogue as gzip JSON Lines files, and see what your organisation has used this month, hour by hour.

  • Exports run in the background, announce themselves with export.completed and keep their files for 7 days
  • GET /v1/usage and /v1/usage/series, with usage.threshold_reached at 80% and 100% of a quota
  • Test mode is counted and shown, never capped

Dated API versions

  • API
  • Webhooks

Name a version in the FurniOps-Version header and its shape never changes under you. Breaking changes ship only in a new dated version.

  • An organisation is pinned to the version it first used
  • Each webhook endpoint has its own version, named in every delivery

The furniops CLI

  • Developer tools

Sign in from the browser, forward live events to a handler on your laptop, signed like real deliveries, and tail the event stream.

  • furniops listen needs no tunnel: it reads the stream and posts each event to localhost
  • furniops trigger emits sample events in test mode
  • Released as a git tag of furniops-packages; not on npm yet

The TypeScript SDK

  • Developer tools

Every API route as a typed method, with auto-pagination, retries, idempotency keys, typed errors, a change stream that reconnects and webhook verification.

  • No dependencies: fetch and Web Crypto, in Node, Deno, Bun and Workers
  • Distributed by git tag; not on npm yet

Test mode with a sandbox catalogue

  • API
  • Platform

Every organisation now has a sandbox catalogue, seeded with sample products, reached with fo_test_ keys. The API, change feed, stream and webhooks behave the same in both modes.

  • Nothing crosses between modes: a live product's ID answers 404 to a test key
  • POST /v1/test/events sends a sample event to your endpoints

Matching across vendors

  • Matching

The same product from different sources becomes one record with a stable ID: matched on identifiers, then scored on text and pictures, with a review queue for the close calls.

  • Merges can be undone, and IDs stay stable through both
  • Matching learns from the pairs people merge and dismiss

Webhooks, the change feed and the live stream

  • Webhooks
  • API

Every price, stock and content change reaches your systems three ways: signed webhooks, an ordered change feed you can replay for 30 days, and a live stream that resumes.

  • Standard Webhooks signatures, retried for about three days, with a delivery log and replay
  • Thin events with what changed, or fat events with the whole object
  • The change feed long-polls, so a consumer hears of a change as soon as it is written

Single sign-on

  • Identity

Connect your organisation's OpenID Connect identity provider, prove your domain with a DNS record, and require SSO for everyone on it.

  • A test sign-in must pass before a connection can be turned on
  • Passkeys, authenticator apps and recovery codes for everyone else