Determine how integrators actually pull data from Otodata's Nee-Vo propane tank monitoring portal, since no public self-serve API documentation is indexed
domain: otodatatankmonitors.com · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the customer-facing product is the Nee-Vo portal/app (neevo.otodata.ca) for viewing tank levels, consumption analytics, and alerts
Note Otodata's marketing copy mentions linking to 'existing management software via API' for ERP/ordering-system integration, but this is described as a partner/enterprise integration, not a published self-serve developer portal
Observe that hobbyist integrations (Home Assistant, HomeSeer) instead reverse-engineer the Nee-Vo portal login to pull data, indicating no public API was available to them
Before committing to an integration path, contact Otodata's sales/support channel directly to ask whether self-serve API credentials are obtainable outside a full ERP-partner agreement
Known gotchas
Don't treat the ERP-integration mention on Otodata's marketing site as evidence of open API docs — it reads as a sales-contact-gated enterprise feature
Nee-Vo/Otodata is a distinct company from Tank Utility and Anova; don't conflate their platforms or ownership
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?