The permissioned EV event & policy layer

Turn EV charging signals into business actions.

Vehicle APIs connect the car. Nerava verifies the charging event, evaluates partner rules, and delivers the right action to applications, APIs, and enterprise workflows.

  • Soket Club live
  • Tesla + Smartcar connections
  • Partner portal live

Platform boundary

From vehicle signal to business outcome

Vehicle connectivity tells an application what happened to the car. Nerava determines what the event means for the business and what should happen next.

Inputs

  • Smartcar
  • OEM APIs
  • Charger data
  • Loyalty
  • Commerce
  • Reservations

Nerava Charge Signals

  • 1Verify the event
  • 2Evaluate the rules
  • 3Deliver the action
  • 4Record the outcome

Applications

  • Partner app
  • Webhook
  • Benefit
  • Outcome record
  • Intelligence feed
  • Enterprise workflow

Core capabilities

Four primitives. Every use case maps back to these.

The “policy layer” is campaign rules in production — consent, eligibility, budget, and frequency evaluated before any action fires.

Verified Events

Convert fragmented vehicle, charger, and partner signals into a canonical, auditable EV event with source evidence and confidence.

Campaign Rules

Evaluate consent, location, time, charging status, eligibility, frequency, budget, and program conditions before any action fires.

Outcome Delivery

Send signed webhooks, trigger benefits, and update partner systems when rules qualify — with a linked outcome record.

Intelligence

Understand driver cohorts, location behavior, program performance, and linked outcomes from the event history.

How it works

Connect → Verify → Evaluate → Deliver → Record

1

Connect

A driver authorizes vehicle access once through a partner experience or Soket Club.

2

Verify

Nerava reconstructs a canonical charging session from vehicle and site evidence.

3

Evaluate

Campaign rules check consent, eligibility, location, time, budget, and frequency.

4

Deliver

Qualified actions fire as webhooks, benefits, or partner-system updates.

5

Record

Source event, decision, delivery, and downstream outcome stay linked for audit and learning.

Vehicle-side intelligence

Add consented vehicle-side intelligence to charger-side data

Nerava provides pseudonymous, driver-authorized session and cohort intelligence that infrastructure data alone cannot show — built for charger intelligence and enterprise mobility platforms.

Delivery today is partner-scoped API access and portal analysis. Scheduled flat-file feeds are on the roadmap for enterprise buyers who already consume infrastructure data that way.

Available now

  • Verified vehicle-side charging sessions
  • Session confidence and source evidence
  • Cohort and program views in Partner Portal
  • Partner-scoped API access to session history

Expanding next

  • First-time versus repeat visitation
  • Cross-network behavior patterns
  • Benefit and commerce outcome joins
  • Recipient- and purpose-level export controls

Live today

The consented pipeline is live in production systems.

Drivers already connect, consent, and generate verified sessions. Early partners operate campaigns and outcomes on that ledger today — scale is growing with each deployment.

Vehicle connection

One-time consented link via Tesla Fleet and Smartcar.

Consent Center

Required acknowledgement plus revocable partner scopes.

Verified session history

Per-session records tied to source evidence.

Soket Club

Driver-facing membership with missions, safety, and benefits.

Partner Portal

Campaigns, outcomes, sites, cohorts, and reporting.

Developer APIs

Partner-scoped endpoints for sessions, grants, and webhooks. Docs portal still expanding.

Compounding advantage

Every rule execution makes the platform more valuable.

The defensible asset is not a list of partner rules. It is the accumulated history of which rules ran, why a driver qualified, what action was delivered, and what business outcome followed.

Sponsored benefits help partners acquire and retain connected drivers. The resulting event and outcome history powers higher-value intelligence and enterprise programs.

1

Consented vehicle

2

Verified event

3

Campaign rules evaluated

4

Decision made

5

Action delivered

6

Outcome observed

7

Performance history accumulates

Business model

Partners pay Nerava to activate and learn from connected EV relationships. Drivers stay free.

Benefits and sponsored programs help partners acquire, retain, and influence connected drivers. The resulting event and outcome history powers higher-value intelligence and enterprise programs.

Platform access

Monthly partner minimum for workspace, campaigns, and operator tools.

Active connections

Pricing tied to active connected vehicles in a partner program.

Verified outcomes

Per eligible event or completed program action when rules qualify.

Intelligence and APIs

Subscription, dataset, or usage pricing for feeds and exports.

Consent & security

Permission infrastructure for EV applications

Vehicle access is explicit and revocable. Downstream partner access is scoped by partner key and consent category — a second layer on top of vehicle-API consent, not a replacement for it.

Read the security overview
  • Explicit vehicle authorization via OAuth (Tesla Fleet, Smartcar)
  • Revocable partner and category scopes for downstream use
  • Partner-scoped API keys and workspace isolation
  • Consent Center acknowledgement before ledger storage
  • Audit-friendly session and grant history
  • Data minimization on partner delivery paths

Build the post-connect layer without rebuilding it

Launch charging benefits, validation, intelligence, or enterprise workflows on driver-authorized EV events.