Sheeva
Sheeva.AI (legally Parkofon Inc.) builds transaction infrastructure for connected vehicles. Its SheevaConnect platform lets a vehicle discover nearby Sheeva Pay outlets, authenticate the driver, and pay for real-world services - fueling, EV charging, parking, tolling, QSR and curbside pickup, and car wash - directly from the infotainment system, using patented location intelligence (SheevaLocate, SheevaFence) and tokenized in-vehicle payments (SheevaPay). The SheevaConnect partner API 2.0 exposes drivers, vehicles, sessions, service hubs, payments, wallets and cards, loyalty, feedback, and HMAC-signed status webhooks across US and India regions.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Sheeva the way a machine reads it — 20 machine-readable artifacts across 15 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Sheeva scores 48.9/100 (developing), with a separate agent-readiness read of 75/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Sheeva
Each block below is one kind of artifact we hold for Sheeva. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 15
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Sheeva Authentication API
The Authentication API from Sheeva — 1 operation(s) for authentication.
Sheeva Credit Cards API
The Credit Cards API from Sheeva — 5 operation(s) for credit cards.
Sheeva Driver Alerts API
The Driver Alerts API from Sheeva — 2 operation(s) for driver alerts.
Sheeva Driver API
The Driver API from Sheeva — 5 operation(s) for driver.
Sheeva Feedback API
The Feedback API from Sheeva — 3 operation(s) for feedback.
Sheeva Loyalty API
The Loyalty API from Sheeva — 2 operation(s) for loyalty.
Sheeva Parking API
The Parking API from Sheeva — 2 operation(s) for parking.
Sheeva Payments API
The Payments API from Sheeva — 3 operation(s) for payments.
Sheeva Service Hubs (Points Of Interest) API
The Service Hubs (Points Of Interest) API from Sheeva — 2 operation(s) for service hubs (points of interest).
Sheeva Session API
The Session API from Sheeva — 7 operation(s) for session.
Sheeva Transactions API
The Transactions API from Sheeva — 3 operation(s) for transactions.
Sheeva UPI API
The UPI API from Sheeva — 2 operation(s) for upi.
Sheeva Vehicle API
The Vehicle API from Sheeva — 3 operation(s) for vehicle.
Sheeva Vehicle Events API
The Vehicle Events API from Sheeva — 1 operation(s) for vehicle events.
Sheeva Webhooks API
The Webhooks API from Sheeva — 3 operation(s) for webhooks.
Scroll within the panel for all 15 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
sheeva-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Sheeva Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Sheeva — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/sheeva · machine-readable index on apis.io