VisionAI and blockchain for the complete container lifecycle.Explore the platform →

Technology

The Ledger Engineered for Freight Logistics.

A permissioned ledger, secure document storage, identity services, event-driven integrations and AI-assisted decisions, designed around how container transportation actually works.

Developer API Hub
The Anchoring Pipeline

From Paperwork to Proof in Four Steps

01

Ingest Payload

A record payload arrives from your TMS, driver app, terminal gate TOS, or REST API endpoint.

✓ Automated Step
02

Hash & Sign

The full JSON payload is fingerprinted with SHA-256 and signed with Ed25519 cryptographic key pairs.

✓ Automated Step
03

Record on Ledger

The hash, signature and timestamp are committed to the permissioned ledger and linked to the related shipment events.

✓ Automated Step
04

Verify Later

Authorized parties can recompute the hash to confirm a document matches the version originally submitted.

✓ Automated Step

For developers

Developer APIs & Provided Services

Connect your TMS, gate system, or ERP to Drayage Blockchain using high-speed REST endpoints, SDKs, and webhook subscriptions.

POST /v1/records/anchorCore Service

Record Anchoring Service

Transform ordinary freight documents (Rate Confirmations, BOLs, PODs) into immutable on-chain ledger entries.

SHA-256 · Ed25519 Multi-Sig
GET /v1/records/verify/:hashInstant Verification

Verification & Audit Engine

Instantly check cryptographic authenticity, parent block height, signature validity, and event tamper status.

<120ms Latency · Global CDN
POST /v1/telemetry/eventTelemetry Stream

Container Custody Ingestion

Stream real-time gate-in, gate-out, chassis swap, and rail ramp handoff events directly from TOS or driver mobile apps.

NTP Timestamped · Zero-Knowledge
POST /v1/webhooks/subscribeEvent Automation

Real-Time Webhook Subscriptions

Receive instant push HTTP callbacks when load milestones are signed, anchored, or verified by partner nodes.

HMAC Signed · Auto-Retry

How Services are Provided & Integrated

Integrate record anchoring and cryptographic verification with just a few lines of code. Our official SDKs auto-generate SHA-256 fingerprints, handle Ed25519 signing, and manage block retries.

REST API & GraphQL Compatibility
SDKs for Node.js, Python, Go, Java, and cURL
Instant Sandbox Key Generation
drayage-api-example
curl -X POST https://api.drayageblockchain.com/v1/records/anchor \
  -H "Authorization: Bearer drc_live_key_9f82a1" \
  -H "Content-Type: application/json" \
  -d '{
    "containerNumber": "MSCU1234567",
    "recordType": "RATE_CONFIRMATION",
    "origin": "Port of Los Angeles Pier 400",
    "destination": "Commerce Intermodal Yard, CA",
    "agreedRateUsd": 1850.00,
    "signerIdentity": "CarrierNode_421"
  }'

About

Building the Trust Layer for Modern Freight

Drayage Blockchain is a transportation technology initiative bringing the operational relationships of drayage into a shared digital environment, where authorized participants work from consistent information and important transactions carry a verifiable history.

Permissioned

Participation, submission and data access follow defined roles and agreements.

Linked history

Corrections are recorded as new events linked to the original, never overwritten.

People in authority

AI recommends; payments, commitments and disputes need defined review.

Talk to the team

Talk to Our Integration Engineering Team

Have questions about TMS API integration, custom validator node deployment, or enterprise pricing? Our team responds within 1 business hour.

⚡ SLA Support: 24/7 Monitoring & Dedicated Account Engineers
📍 Headquarters: San Pedro Bay Logistics Tech Hub, CA
Frequently Asked Questions

Developer & Security FAQ

Is sensitive commercial pricing data public on the chain?+

No. Only cryptographic SHA-256 hashes, digital signatures, and timestamps are committed on-chain. Underlying document payloads remain securely stored in your private TMS or ERP system.

Do carriers or shippers need a blockchain account to verify a record?+

No. Anyone with the record file or payload can use our public verification engine to check authenticity. Accounts are only needed to issue API keys for anchoring new records.

How are corrections or load amendments handled?+

If a rate or load detail changes, an updated record version is anchored with a link referencing the parent transaction. The audit trail retains full immutable history of both versions.

Does a blockchain record prove the physical event happened?+

No. The ledger makes an accepted record difficult to alter without detection. Confirming that a pickup, delivery, inspection or return actually occurred still depends on trustworthy source systems, authenticated participants and supporting evidence.