Edge library
New integration path for Amazon CloudFront, as a release candidate: kit
0.1.0-rc.3, a CloudFront Function that
sends AI-agent requests to a Lambda that reads the page through your distribution and runs the edge library 1.1.4.
Qualified on 28 October 2026 with the doubleshift API and reads by AI assistants. Download:
https://api.shftd2.com/edge/cloudfront/doubleshift-cloudfront-kit-0.1.0-rc.3.zip. The kit is © DS Technologies,
all rights reserved; its LICENSE grants doubleshift account holders the right to run it on their own
distributions. Installation: Amazon CloudFront.SHA-256 of the archive, kit 0.1.0-rc.3
SHA-256 of manifest.json, kit 0.1.0-rc.3
Edge library
Adds
scope: include and exclude paths limit the pages the library works on; outside them, no call
and no record. The console’s Worker code carries the paths of the routing rules you select.SHA-256
Docs
The documentation now has two tabs. Guides holds 13 pages, from the Quickstart to verification.
API reference holds the delivery API, with a page generated for
GET /v1/fragment, the edge
library, and the management API in its last group. This changelog is new. Five former URLs redirect
to their new pages.Docs
The documentation now uses the doubleshift brand system: blue accent, Inter, the brand icons, and
diagrams in the brand colors. HTTP status codes appear as inline code. No page, URL or contract changed.
Edge library
Edge integration now says where delivery records go: direct delivery logs, Cloudflare Logpush (a logs
token for Logpush from doubleshift, a Logpush job on your account, Workers Paid plan), or your own logs
only. The Delivery logs API page is renamed Direct delivery logs API.
Edge library
Adds direct delivery logs: with
logsToken set, the library sends each delivery record to doubleshift in
the background. New options quietInfo and skipIfEnriched.SHA-256
Edge library
POST https://logs.shftd2.com/v1/beacon receives one delivery record per request, authenticated by a logs
token that is separate from your API key. The library uses it from 1.1.3; a custom sender may use the
same contract. The reference page lists the record format and response codes.Edge library
The card no longer carries
role="complementary". When deliveryCode is enabled, the delivery code is
added to the in-content brand line.SHA-256
Edge library
Adds delivery-record identifiers: each record carries
record_id, and after an answer status and
api_rid; card_written once the card is inserted. The card’s root carries its delivery number in
data-ds-delivery.SHA-256
Delivery API
Every response of
GET /v1/fragment, whatever its status, carries its delivery
number in X-Request-Id. An X-DS-Record-Id request header holding a UUID is kept with the delivery;
any other value is ignored.Edge library
One pass over the page. The card is built at the edge from the JSON answer. On any outcome without a
card, the origin page is returned as is.
SHA-256
Edge library
First release of
doubleshift-edge.v1.js, one file for a Cloudflare Worker. It calls GET /v1/fragment
for AI agents only, inserts the card before the first content container, and serves the page unchanged
if anything fails.SHA-256
Management API
New management API on
https://api.shftd2.com/v1: create and update sites, fragments, the site default,
routing rules, card eligibility and API keys from a script. Calls use a management token
(Authorization: Bearer) that an organisation owner creates in Settings → Management tokens.ConsoleManagement API
Cards are targeted by eligibility. A card with no fragment selected stays eligible everywhere in your
account; a card with fragments selected is eligible only on those. The console, the management API and
the docs call this “eligibility”.
Delivery API
New
GET /v1/fragment: send partner_id and page_url; doubleshift resolves the fragment from the page
(routing rule, then the site default). The key goes in X-API-Key only. Every response is
Cache-Control: private, no-store.