https://api.truckaurbus.com, without a key; they are not under /v1 yet.
The commitment ledger
Every forecast Edge publishes is sealed the moment it is published and scored once against the outcome on its day, by the method its own entry states. A scored forecast is never rescored.disclosure is what a reader must know while a forecast waits, in English, with Hindi and Tamil under words.hi.disclosure and words.ta.disclosure; it is empty for most forecasts. A forecast on the yard sealed before the yard’s first real sale carries one, and its verdict carries the same words in note once it is scored. No new forecast on the yard is sealed until the yard has a real sale, and no figure on Edge is read from a round held before the yard opened to the public.
due_on is the day the outcome is read: the horizon, or a later day when the outcome could not be read on the horizon (a sale still waiting for the seller’s approval); then deferred_to carries the new day and deferred_reason why, so a date never moves silently. overdue is true for a forecast still pending after its due_on. The verdict’s words are in note, why_band and method_change in English and under words.hi and words.ta in Hindi and Tamil.
To verify a row, take commitment as UTF-8 and hash it with SHA-256; it must equal sha256. The commitment text is the key, the statement, the predicted value, the floor, the ceiling, the horizon and the sealing time, joined with a vertical bar. A hit is an outcome inside the band, floor and ceiling included. kind is operational for something Edge counts itself and market for something outside Edge that anyone can check. The protocol and a verifier that checks the whole ledger from this endpoint are at github.com/truckaurbus/commitment-ledger.
Releases
GET /catalogue/edge/releases returns counted_at (the latest count) and releases, one row per release: key, section (repos, models, nazar, atlas, factory), name, grade, counted_at and note. The grades are counted every morning with the products’ grades: a grade the evidence no longer holds moves down with its note, and a higher one waits for a person. The Releases page prints these grades and nothing typed.
Products and grades
Every product carries a grade and the date the grade was last confirmed. The grade words arelive (read from production), modelled (from a stated method on this data), pilot (running with consenting clients) and next (named and priced, not yet built). The grade never moves on interest; it moves on evidence, and the note says where the product stands today.
unit always travels. band carries the price only where it is public, which is the transactional products: a single valuation, a certificate, a decision. For licences, memberships, maker subscriptions and the seats band is null and the desk quotes, by category and book size.
The outcome loop, for partners
A partner who holds an Edge key posts its consented enquiries into the loop, Edge asks the operator at thirty and sixty days whether they bought and what, and the partner reads its own rows back. No identity column is stored on the enquiry; the contact used for the asks is purged after the second ask. Keys are issued by the desk (write to edge@truckaurbus.com). Send yours asX-Edge-Key. Every row a key posts stays in that key’s tenant; a key never reads another partner’s rows.
bought as yes, not_yet or no, the variant bought where known, and a reason from price, finance, delivery, dealer, spec, service, resale or other, with free text. GET /catalogue/edge/outcomes/stats publishes the loop’s own response rate and its grade, so the loop is held to the same standard as everything else on Edge.
The Residual Index
The register’s own curve: the new price on the register, the age, the kilometres against the class norm, the yard’s closes and the on-road rules, one arithmetic on every Truckaurbus surface. In public the index prints a teaser: the class norm, one point of the curve and the yard’s last quarter. The curve itself, the kilometre rule and the band are part of the Residual Index licence.vehicle or variant, year, km, state_code, body_type) and returns the same packet with the kind valuation; verify it the same way. Valuations never appear on the desk’s decision list.
The underwriting desk
A loan file in, a decision packet out. The packet carries the valuation on the register’s own new price with the register’s one depreciation arithmetic, the band, the grade, the loan-to-value, the Body Book check on the declared body, the red flags as stated rules, an evidence list with a source, a date and a grade on every line, and a hash sealed the moment the packet is made. Every decision is metered at your contract’s price and appears on the monthly statement. Send your key asX-Edge-Key; a member of your tenant may also call with their own sign-in token.
vehicle is the vehicle as written; pass variant with a register slug instead when you have it. When more than one vehicle matches, the desk answers 422 with up to three candidates to choose from.
commitment with SHA-256 as UTF-8; it must equal sha256. The commitment is the word desk, the decision id, your tenant id, the kind, the register slug, the year, the kilometres, the state, the figure, the floor, the ceiling and the sealing time, joined with a vertical bar. A hit is an outcome inside the band. The desk’s aggregate accuracy is published from these verdicts every quarter.
The Body Book certificate
A certificate at variant level: what the register knows about bodies on one chassis, by stage (declared by the maker, observed in the register’s photographs, ratified by body builders), and the verdict on the body a file declares. Numbered, sealed with a hash, issued to your tenant, metered per certificate; the PDF carries the hash, the verification address and its QR code. Anyone can verify a hash in public; the verification never names who the certificate was issued to. The per-vehicle Passport by chassis number comes with the insurer pilot.ratified, observed, declared, not_on_register, or chassis when no body was declared. The commitment is the word certificate, the certificate id, your tenant id, the register slug, the body type, the verdict and the issue time, joined with a vertical bar; its SHA-256 is the hash.
The public instruments
Every product page on edge.truckaurbus.com carries an instrument above the fold. The demo instruments compute live on a sample vehicle from the register and store nothing; the live ones read the register this minute. All are public, all carrycounted_at, and every figure in them comes from these endpoints.
The product record (
GET /catalogue/edge/products) now carries price_kind (full, floor, pilot, included, fees, fixed, book), price_low_inr, price_high_inr and price_unit; every price line on Edge is composed from these. The forecast record (GET /catalogue/forecasts) carries why_band and method_change, written when a forecast is scored, and the verdict note at edge.truckaurbus.com/{locale}/verdicts/{key} is rendered from them.
Two more public reads serve the product pages: GET /catalogue/edge/passport/sample returns the desk’s own sample certificate (a real one, issued to the house on a real chassis) so the verifier can be tried at once, and GET /catalogue/edge/counter/demo?kind=launch-reception|why-we-lost|demand returns an illustrative packet for the Counter’s pages, built on real entities with counts that are illustrative and say so; nothing in a demo packet is a person or a stored record.