Tank Utility website screenshot

Tank Utility

Tank Utility makes LTE-connected propane tank monitors, mobile apps, and a read-only API that surface their data. Its sensors report tank fuel level, temperature, and battery state so homeowners get low-fuel alerts and fuel marketers can route deliveries by real consumption instead of guesswork — Tank Utility says this drops the same gallons in up to 40% fewer deliveries. The Tank Utility API lets an account exchange credentials (HTTP Basic) for a short-lived token, list the monitors on the account, and read each device's latest reading. Tank Utility is owned by Anova.

Tank Utility publishes 2 API contracts indexed on the APIs.io network: Authentication API and Devices API. Tagged areas include Propane, Tank Monitoring, IoT, Fuel Delivery, and Telemetry.

The Tank Utility catalog on APIs.io includes 1 Spectral governance ruleset.

Tank Utility’s developer surface includes authentication, CLI, support, engineering blog, and 16 more developer resources.

24.6/100 emerging ▬ flat Agent 33/100 agent ready Front door AI 1/6 silent Heartbeat 0/100 dormant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
1 published contract 1 Agent Skills
PropaneTank MonitoringIoTFuel DeliveryTelemetryEnergySensorsCompany

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0
Regulatory Posture applies to this provider. Its tags matched the Energy & Utilities regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics does not apply to this provider. The published contracts declare no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's denominator entirely — not scored zero. A reference or data API is not deficient for being unable to upsert.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for Tank Utility It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/tank-utility/"><img src="https://apis.io/badge/tank-utility/card.svg" alt="Tank Utility on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
  • Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
  • A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
  • Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
  • Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
  • Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
5 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/tank-utility/apis.yml: open an issue on github.com/api-evangelist/tank-utility to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

measured — observed by APIs.io (published)

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Tank Utility Authentication API

Exchange account credentials for a short-lived API token.

Tank Utility Devices API

List and read propane tank monitor devices.

Open Collections 2

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Arazzo Workflows 1

Multi-step API workflows described with the Arazzo specification.

Tank Utility — read propane tank level

Authenticate to the Tank Utility API, list the propane monitors on the account, and read the latest reading (fuel level %, temperature) for the first device.

ARAZZO

Agent Skills 1

Packaged agent skills for driving this provider's APIs from an AI assistant.

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Tank Utility API Rules

58 rules · 56 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Tank Utility Devices Overlay

2 actions · update · tank-utility-devices-openapi.yml

DERIVED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Tank Utility Authentication

apiKey/http · 2 schemes

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: tank-utility
name: Tank Utility
description: Tank Utility makes LTE-connected propane tank monitors, mobile apps, and a read-only API that surface their data.
  Its sensors report tank fuel level, temperature, and battery state so homeowners get low-fuel alerts and fuel marketers
  can route deliveries by real consumption instead of guesswork — Tank Utility says this drops the same gallons in up to 40%
  fewer deliveries. The Tank Utility API lets an account exchange credentials (HTTP Basic) for a short-lived token, list the
  monitors on the account, and read each device's latest reading. Tank Utility is owned by Anova.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://tankutility.com/wp-content/uploads/2025/06/logo_merge.png
url: https://raw.githubusercontent.com/api-evangelist/tank-utility/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- bullpen-capital
x-tier: stub
x-tier-reason: portfolio-lead
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 18
  pass: local-v1
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Propane
- Tank Monitoring
- IoT
- Fuel Delivery
- Telemetry
- Energy
- Sensors
- Company
apis:
- aid: tank-utility:tank-utility-authentication-api
  name: Tank Utility Authentication API
  description: Exchange account credentials for a short-lived API token.
  humanURL: https://tankutility.com
  baseURL: https://data.tankutility.com/api
  tags:
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/tank-utility-authentication-api-openapi.yml
  - type: Authentication
    url: authentication/tank-utility-authentication.yml
- aid: tank-utility:tank-utility-devices-api
  name: Tank Utility Devices API
  description: List and read propane tank monitor devices.
  humanURL: https://tankutility.com
  baseURL: https://data.tankutility.com/api
  tags:
  - Devices
  properties:
  - type: OpenAPI
    url: openapi/tank-utility-devices-api-openapi.yml
  - type: Authentication
    url: authentication/tank-utility-authentication.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: X-MCPServerCandidate
  url: mcp/tank-utility-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: DomainSecurity
  url: security/tank-utility-domain-security.yml
- type: Authentication
  url: authentication/tank-utility-authentication.yml
- type: Conventions
  url: conventions/tank-utility-conventions.yml
- type: ErrorCatalog
  url: errors/tank-utility-error-codes.yml
- type: Lifecycle
  url: lifecycle/tank-utility-lifecycle.yml
- type: DataModel
  url: data-model/tank-utility-data-model.yml
- type: Conformance
  url: conformance/tank-utility-conformance.yml
- type: Packages
  url: packages/tank-utility-packages.yml
- type: CLI
  url: cli/tank-utility-cli.yml
- type: Overlay
  url: overlays/tank-utility-devices-overlay.yaml
- type: LLMsTxt
  url: llms/tank-utility-llms.txt
- type: AgentSkill
  url: skills/_index.yml
- type: Arazzo
  name: Read propane tank level
  url: arazzo/tank-utility-read-tank-level.yml
- type: Support
  url: https://support.tankutility.com/hc/en-us
- type: Blog
  url: https://tankutility.com/blog/
- type: Login
  url: https://portal.tankutility.com
- type: TermsOfService
  url: https://tankutility.com/tos/
- type: PrivacyPolicy
  url: https://www.anova.com/privacy-policy/
- type: Website
  url: https://tankutility.com

Tank Utility API — frequently asked questions

Does Tank Utility have an API?

Yes. APIs.io lists 2 APIs from Tank Utility, including Tank Utility Authentication API and Tank Utility Devices API.

Is there an OpenAPI specification for the Tank Utility API?

Yes. APIs.io indexes 2 OpenAPI specifications for Tank Utility, each linked for download from this page.

How do I authenticate with the Tank Utility API?

Tank Utility uses bearer-token authentication (apiKey/http · 2 schemes). The details are profiled on APIs.io as Tank Utility Authentication.

Is the Tank Utility API ready for AI agents?

Tank Utility has a Kin Score of 24.6 out of 100 (emerging) and an Agent Readiness score of 33.1 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/tank-utility"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/tank-utility/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/tank-utility/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.