Skip to main content
Edge is the reference layer of India’s commercial vehicle economy, run by Truckaurbus at edge.truckaurbus.com. Everything the site prints comes from the endpoints below, and everything below is public except the partner rows. These paths are read directly on 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 the day its horizon closes. A scored forecast is never rescored.
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.

Products and grades

Every product carries a grade and the date the grade was last confirmed. The grade words are live (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 why.
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 as X-Edge-Key. Every row a key posts stays in that key’s tenant; a key never reads another partner’s rows.
The answer carries 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 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 as X-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.
To verify a packet, hash 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.