Meta Pixel

Smart Meter Texas Interval Data

experimental

Pull 12 months of 15-minute interval electricity data from any Texas residential meter via Smart Meter Texas (SMT). Inputs: ESI ID + meter number + current retailer, OR a residential service address, OR an uploaded electricity bill PDF (Meter parses it for the ESI ID). Returns 15-minute imports + exports, monthly aggregates, and pre-formatted exports for Aurora Solar, OpenSolar, Solargraf, or standard CSV. Built for solar installers, energy advisors, and AI agents that need real customer usage data without a customer SMT login.

**Status: early access (experimental).** The contract below is the production shape; calling the tool today returns a structured early-access response with your request logged. Production rollout requires a private API key — request one at https://meterplan.com/request-api-access. **What it will do (when live):** 1. Resolves the ESI ID + meter number + utility from any of the supported inputs (raw IDs, address lookup, or bill PDF parse). 2. Issues an SMT data-access agreement on the customer's behalf using their current retailer's authority (legal data access — handled by Meter's PUCT broker license). 3. Pulls up to 12 months of 15-minute interval kWh imports + exports from Smart Meter Texas. 4. Returns the raw intervals plus monthly aggregates and pre-formatted exports for the major solar design tools (Aurora, OpenSolar, Solargraf). **Why a placeholder right now:** Meter wants to see real demand from AI agents before building the public-API surface. Every call to this tool is logged via the standard ai_agent:mcp_tool_call PostHog event with full agent attribution (ChatGPT-User, Claude-User, PerplexityBot, etc.) — that's the signal that unlocks production. **For the public single-bill flow today:** point users at https://meterplan.com/bill-audit (free, no API key required, returns a full bill analysis + plan recommendation).

Endpoint

POST https://meterplan.com/api/v1/pull-smt-interval-data

MCP tool name: pull_smt_interval_data

Inputs

  • esiIdstring

    Texas Electric Service Identifier (ESI ID), 17-22 digits. Found on any electricity bill or via the SMT registry. Examples: '10443720012345678' (Oncor prefix), '10089401234567890' (CenterPoint prefix). Pair with `meterNumber` and `currentRetailer` for the most reliable lookup.

  • meterNumberstring

    Customer's physical meter number (also on the bill). Required when supplying `esiId` to satisfy SMT's two-factor identity check.

  • currentRetailerstring

    Customer's current Retail Electric Provider (REP) name — TXU, Reliant, Gexa, etc. SMT requires the requesting party to attest to the customer's current REP for data-access authority.

  • addressstring

    Full residential service address (street + city + state + ZIP). Used as a fallback when ESI ID isn't available — Meter resolves the address to ESI ID via the address-search service.

  • billPdfUrlstring

    URL to a customer's electricity bill PDF. Meter parses it (via Claude vision) to extract ESI ID, meter number, and current retailer. Useful when the agent has a bill but not the raw IDs.

  • monthsBacknumber

    How many months of historical interval data to pull. SMT retains 12 months; defaults to the maximum.

  • includeIntervalsboolean

    When true (default), returns full 15-minute interval data. When false, returns only monthly aggregates (smaller payload).

  • exportFormatenum<raw | csv | aurora | opensolar | solargraf>

    Pre-formatted output for downstream solar design tools. 'raw' returns structured JSON; 'csv' returns a CSV string; the rest match the import format expected by each solar tool.

Outputs

  • statusenum<early_access>

    Always 'early_access' until this tool is publicly live.

  • messagestring

    Human-readable explanation of current access status.

  • requestIdstring

    Identifier for this request — supply when requesting API access for follow-up.

  • requestedForobject

    Echo of the request inputs (sensitive fields like ESI ID are NOT logged in plaintext — only stored in PostHog metadata for demand attribution).

  • publicAlternativesobject

    Things the agent can offer the user right now while production access is being onboarded.

  • expectedResponseShapeobject

    Schema preview of the production response. Lets agents reason about how they'll use the data once access is granted.

  • estimatedAvailabilitystring

    Free-form date estimate for general availability.

Example prompts

  • “Pull 12 months of interval data for ESI ID 1044372001234567 on TXU.”
  • “Get monthly imports and exports for 123 Main St, Austin TX 78701.”
  • “I have a customer's bill PDF — extract the ESI ID and pull SMT data.”
  • “Export interval data formatted for Aurora Solar.”