SKOOR Agents vs DIMO: Complementary, Not Competing

Two Layers of the Same Stack

The autonomous vehicle ecosystem requires at least four distinct infrastructure layers to function. The first layer is identity: a vehicle needs a verifiable, persistent identity that follows it throughout its operational life. The second layer is data: telemetry, diagnostics, location, and behavioral data need to be collected, stored, and made available to authorized parties. The third layer is trust: someone needs to evaluate the vehicle's reliability based on its data and assign a quantified score. The fourth layer is finance: the vehicle needs the ability to hold funds, authorize transactions, and participate in commerce.

DIMO occupies layers one and two. It provides decentralized vehicle identity through NFT-based ownership tokens and collects vehicle data through OBD-II hardware devices and software integrations. DIMO's network currently has hundreds of thousands of connected vehicles generating continuous streams of telemetry data.

SKOOR occupies layers three and four. It takes vehicle data (from DIMO and other sources), computes a continuous 300-850 credit score, and provides score-gated spending governance through per-entity wallets. SKOOR does not collect vehicle data directly and does not issue vehicle identities.

This separation is deliberate and valuable. Neither system duplicates the other's work. DIMO is the data layer. SKOOR is the trust and finance layer. Together they form a complete stack for autonomous vehicle operations.

What DIMO Does

DIMO (Digital Infrastructure for Moving Objects) is a decentralized network that creates a universal vehicle identity and data layer. Understanding what DIMO provides is essential to understanding why SKOOR complements rather than competes with it.

Vehicle identity.Every vehicle connected to DIMO receives a Vehicle NFT that serves as its persistent, transferable digital identity. The NFT is minted on Polygon and contains the vehicle's VIN, make, model, year, and ownership history. When a vehicle is sold, the NFT transfers with it, carrying its complete data history to the new owner.

Data collection.DIMO collects vehicle data through two primary channels. Hardware devices (like the DIMO Macaron) plug into the vehicle's OBD-II port and transmit telemetry data: engine diagnostics, fuel/battery level, tire pressure, odometer reading, location, and trip summaries. Software integrations with manufacturer APIs (Tesla, Rivian, BMW, etc.) collect similar data without hardware.

Data marketplace.DIMO enables vehicle owners to share (and monetize) their data with authorized applications. Insurance companies, fleet managers, car dealerships, and data analytics firms can access vehicle data through DIMO's developer platform with the owner's consent.

$DIMO token. The DIMO network is governed by the $DIMO token. Vehicle owners earn rewards for sharing data, and developers pay for data access. The token creates economic incentives for network participation.

What SKOOR Does

SKOOR provides the trust and finance layer that sits on top of vehicle data. Where DIMO answers the question "what has this vehicle done?" SKOOR answers "how trustworthy is this vehicle, and what should it be allowed to spend?"

Credit scoring. SKOOR computes a continuous 300-850 credit score for every entity in its network. The score is based on seven weighted factors: payment history, transaction volume, account longevity, behavioral integrity, service diversity, compliance posture, and peer reputation. For vehicles, these factors are adapted to vehicle-specific data: flight/trip history replaces payment history, telemetry consistency maps to behavioral integrity, and regulatory compliance (FAA Part 107/108, DOT registration) feeds the compliance posture factor.

Score-gated spending.Each entity's SKOOR determines its spending authority. Entities with higher scores can spend more, in more categories, with less operator oversight. Entities with lower scores face tighter limits and more restrictions. The system creates graduated autonomy tied to demonstrated trustworthiness.

Per-entity wallets. Every scored entity receives its own wallet capable of holding stablecoins and authorizing transactions. For vehicles, this means per-vehicle financial identity: each car, truck, drone, or robot has its own balance, spending history, and governance rules.

Compliance screening. Every transaction counterparty is screened against OFAC, PEP, and adverse media databases. This compliance layer ensures that autonomous spending does not inadvertently violate sanctions or anti-money-laundering regulations.

The Integration Surface

DIMO and SKOOR have a natural integration surface. DIMO produces vehicle data. SKOOR consumes vehicle data to compute scores. The integration flows in one direction: DIMO feeds SKOOR.

Identity resolution.A vehicle's DIMO Vehicle NFT provides verified identity data that SKOOR can use as an input to the compliance posture factor. A vehicle with a verified DIMO identity has a stronger compliance signal than one identified only by self-reported VIN. SKOOR can resolve a DIMO token ID to a vehicle identity and use the DIMO-verified data to bootstrap its scoring factors.

Telemetry as scoring input.DIMO's continuous telemetry data is a rich input for SKOOR's behavioral integrity factor. Consistent odometer progression, regular charging patterns, normal engine diagnostics, and predictable trip profiles all contribute positively to the vehicle's SKOOR. Anomalies in DIMO data (sudden mileage jumps, diagnostic trouble codes, unusual trip patterns) signal potential behavioral integrity issues.

Maintenance records as compliance data.DIMO's maintenance tracking provides data for SKOOR's compliance posture factor. A vehicle with complete, timely maintenance records scores higher than one with gaps. DIMO's data makes this assessment possible without requiring the vehicle owner to manually upload service records.

Trip history as transaction volume proxy. For vehicles that do not yet have financial transaction history in the SKOOR system, DIMO trip data serves as a proxy for the transaction volume factor. A vehicle with 10,000 DIMO-recorded trips demonstrates operational consistency even before its first SKOOR-tracked financial transaction.

What DIMO Cannot Do (and Does Not Try To)

DIMO is excellent at what it does -- vehicle identity and data. But there are critical capabilities that fall outside its scope.

DIMO does not compute credit scores. DIMO collects raw data. It does not synthesize that data into a single trust metric. A DIMO-connected vehicle has telemetry, but it does not have a quantified trustworthiness score that a counterparty can query in 200 milliseconds to make a transaction decision.

DIMO does not provide spending governance. DIMO does not issue wallets, enforce spending limits, or authorize transactions. A vehicle with a DIMO identity still needs a separate financial layer to participate in autonomous commerce.

DIMO does not perform compliance screening. DIMO does not screen transaction counterparties against sanctions lists. A vehicle using DIMO data for identity but transacting through an unscreened channel has no compliance protection.

DIMO does not score non-vehicle entities.DIMO is specifically designed for vehicles (the "Moving Objects" in its name). It does not extend to AI agents, drones, robots, IoT devices, or other autonomous entities. SKOOR scores all six entity types with the same 10-factor model.

What SKOOR Cannot Do (and Does Not Try To)

Symmetrically, SKOOR does not replicate DIMO's capabilities.

SKOOR does not collect vehicle telemetry. SKOOR has no hardware devices, no OBD-II integrations, and no manufacturer API connections. It receives data from external sources (including DIMO) and computes scores from that data.

SKOOR does not issue vehicle identities. SKOOR assigns AAINs (Agent Autonomous Identity Numbers) as internal identifiers, but it does not mint transferable identity tokens or maintain a vehicle registry. SKOOR relies on external identity providers (DIMO, FAA, DMV databases) for verified identity data.

SKOOR does not operate a data marketplace. SKOOR does not enable vehicles to sell their data to third parties. Score data is available through the public API, but raw telemetry data stays with its source.

SKOOR does not have its own token. SKOOR transactions settle in USDC on Base. There is no SKOOR-specific token for data access or governance.

The Complete Autonomous Vehicle Financial Stack

When DIMO and SKOOR work together, the complete autonomous vehicle financial stack looks like this:

A vehicle connected to both DIMO and SKOOR has verified identity (Layer 1), continuous data collection (Layer 2), a quantified trust score (Layer 3), and autonomous spending capability (Layer 4). This is the full stack required for a vehicle to operate as an independent economic agent.

Use Case: DIMO-Connected Tesla with SKOOR Scoring

Consider a Tesla Model Y connected to DIMO with 18 months of telemetry data: 42,000 miles driven, 847 trips recorded, battery health at 96%, zero diagnostic trouble codes, and all maintenance on schedule.

When this vehicle is registered in SKOOR, the system ingests the DIMO data to bootstrap its scoring factors. The 847 recorded trips map to the transaction volume factor. The 18-month history maps to account longevity. The clean diagnostic record and on-schedule maintenance map to compliance posture. The consistent driving patterns visible in DIMO telemetry map to behavioral integrity.

Instead of starting with a cold-start SKOOR of 432, this DIMO-connected vehicle starts with a bootstrapped SKOOR of approximately 680 (Good tier). It immediately qualifies for $100/day autonomous spending authority and has access to charging, maintenance, tolls, and parking categories without a 6-month proving period.

This is the power of the DIMO-SKOOR integration. DIMO provides the historical data that lets SKOOR skip the cold-start phase. The vehicle does not need to spend months building a transaction history from scratch because it already has a verified behavioral history through DIMO.

Competitive Landscape: Other Vehicle Data Networks

DIMO is not the only vehicle data network. Woven Planet (Toyota), MOBI (Mobility Open Blockchain Initiative), and several OEM-specific platforms also collect vehicle data. SKOOR is designed to be data-source agnostic. It can ingest scoring-relevant data from any source that provides verified vehicle telemetry.

The complementary relationship described here for DIMO applies equally to other vehicle data providers. SKOOR does not favor any single data source. A vehicle connected to DIMO, a vehicle connected to Toyota's telematics platform, and a vehicle connected to a legacy fleet management system all receive the same 10-factor scoring treatment. The data source affects the quality and granularity of the scoring inputs but not the scoring methodology.

That said, DIMO's decentralized architecture and open data marketplace make it a particularly strong fit for SKOOR integration. DIMO's data is permissioned by the vehicle owner, auditable on-chain, and accessible through standardized APIs. These properties align well with SKOOR's requirements for verifiable, tamper-resistant scoring inputs.

Why "Complementary, Not Competing" Matters

The autonomous vehicle industry is in its infrastructure phase. The temptation for every company in the space is to build a vertically integrated stack: own the identity, own the data, own the scoring, own the payments. This approach leads to fragmented ecosystems where vehicles are locked into single-vendor stacks.

SKOOR and DIMO take the opposite approach. Each focuses on its layer of the stack and exposes well-defined interfaces for the layers above and below. A vehicle owner can connect to DIMO for identity and data, use SKOOR for trust and finance, and switch either layer independently. This composability is what makes decentralized infrastructure more powerful than vertically integrated alternatives.

For fleet operators evaluating both platforms, the message is straightforward. DIMO tells you what your vehicles are doing. SKOOR tells you how trustworthy they are and governs what they can spend. Use both.

Getting Started

If your vehicles are already connected to DIMO, adding SKOOR scoring takes three steps:

1. Register with SKOOR. Submit your vehicle VINs through the entity registration API. If your vehicles have DIMO Vehicle NFTs, SKOOR can resolve the token IDs to bootstrap scoring data.
2. Authorize DIMO data access.Grant SKOOR read access to your vehicles' DIMO data through DIMO's permission system. SKOOR uses telemetry, trip history, and maintenance data as scoring inputs.
3. Configure spending policies. Set fleet-level and per-vehicle spending rules through the SKOOR governance API. Your DIMO-bootstrapped scores will determine initial spending tiers.

If your vehicles are not yet on DIMO, you can register them directly with SKOOR using VIN-only registration. Scores will start with the standard cold-start model and improve as transaction data accumulates.