Build in public/Honest dates only/4 entries
This changelog is the build-in-public record of Scrapeless Data, and it follows one rule: an entry appears when the thing it describes has actually shipped, dated to the day it shipped. There are no countdown clocks, no teased milestones, and no forward-dated promises. If you want to know what exists today versus what is planned, this page and the machine-readable protocol surface are the two authoritative answers.
The record
Everything below exists and can be verified from this domain today: load the endpoints, view the pages, read the source of the machine surface. Entries are newest first, each dated to the day the work became publicly checkable, and each written specifically enough that you could audit the claim it makes.
The content surface is live: planned pricing with the flat no-token-math structure, the compliance method page, the docs quickstart with clearly labeled synthetic examples, a 21-term glossary with DefinedTerm markup, the team page, and this changelog. Every page now passes a machine copy gate that scans rendered text for banned characters, vendor names, and any phrasing that would overstate what exists today.
The full agent-readable surface shipped: a UCP manifest at /.well-known/ucp, an ACP configuration with accepting_orders set to false and every catalog entry truthfully flagged, an AP2 trust configuration with a published P-256 signing key for did:web:www.scrapelessdata.com, plus llms.txt, agent.json, ai-plugin.json, ai-context.json, and a free protocol check tool at /api/check-endpoint. Mandate issuance and checkout stay off until activation.
The site foundation went up on a server-rendered Next.js app with the design system ported from the company brand spec: alternating ink-navy and cool-light bands, one cobalt ink, one purple signal, no third-party UI dependencies. Every page renders through a shared template that emits compact JSON-LD, a speakable answer capsule, breadcrumbs, and an FAQ block structurally.
The public-claims framework was finalized before any public page was written: design facts in present tense, data availability in future tense, no record counts or coverage claims until a supply contract is executed, planned pricing always labeled as planned. The same rules were encoded as a deny list so the build fails if a page ever drifts from them.
Because a public record of shipped work is the only credibility a pre-launch product can honestly claim. Anyone can publish a roadmap; a dated trail of things that verifiably exist, each checkable the day it appears, is harder to fake and more useful to evaluate. The discipline also runs inward: if a week produces nothing shippable, this page says so by silence, and that silence is information we choose to expose.
Shipped surfaces, contract-shape changes, and status changes that affect what you can rely on: pages going live, protocol endpoints changing shape, documented API contracts being revised, supply contracts moving from in-progress to executed, certification wording being finalized, and eventually keys issuing at activation. Marketing events do not get entries. If an entry ever revises a documented shape, it names what moved and why, so an integration built against the old shape knows exactly what to change.
The next entries this page expects, in whatever order reality delivers them: supply contract execution, certification wording finalized, and API keys issuing at activation. Create an account and you are in launch order when that last one lands.