Everything your team checks before switching a forecast feed.
Documents, turnaround times, and API surfaces procurement teams ask for.
Typical evaluation turnaround
Evaluation path
Enterprise review still starts with evidence.
A commercial conversation is useful only after the buyer understands current live performance, benchmark scope, API fit, and procurement requirements.
- 01
Review live scorecard
Start with the current h24 table, including gaps to ISO references and pending reference rows.
Open scorecard - 02
Request scoped benchmark
Declare grid, horizon, audit period, and decision context before any comparison is scored.
Request benchmark - 03
Test API payloads
Create a free key or inspect the docs, then test responses against your integration shape.
View API docs - 04
Move to procurement or paid plan
Use the trust, SLA, pricing, and enterprise pages when the benchmark is ready for review.
Open procurement
What each team looks at first.
Trading & procurement
Side-by-side MAPE comparison against your current feed. Day-ahead and multi-day accuracy across the markets you trade or serve load in.
Engineering
REST API with bearer auth, JSON/CSV/XML responses, <50ms latency. Standard integration, typically under a day.
Planning & resource adequacy
Long-horizon climate-projection pipeline (WRF + LOCA2-Hybrid, hourly via ERA5 analog matching, uncertainty decomposition) for IRP filings and RA shape requirements. Contact for scope.
Procurement & security
Runs on SOC 2 Type II certified infrastructure providers (Vercel, Supabase). TLS in transit, encrypted storage at rest, API keys stored as hashes. Gramm security documents are available during procurement review.
Operations
Status page, incident communication, named support contact. 99.9% uptime target on Developer, Team, and Growth; Enterprise availability is commercially negotiated.
Five ways to receive forecasts.
REST API and webhooks on all paid plans. SFTP delivery on Growth and Enterprise. Snowflake Share and WebSocket streaming on Enterprise.
Pull forecasts on demand. JSON, CSV, XML. Bearer auth, <50ms response. OASIS-compatible endpoint for CAISO migration.
Forecasts appear directly in your Snowflake account as a shared dataset, no API calls, no pipeline code.
Push delivery for intraday forecast updates. Subscribe to regions and receive updates the moment a new run completes.
Scheduled CSV/XML file drops to your secure server.
HTTP callback when a new forecast run completes. Trigger your downstream pipeline automatically, no polling required.
pip install gramm. Typed client with pandas DataFrame output. Handles auth, retries, and caching. Open source on GitHub.
How your data is handled.
Infrastructure
Hosting, database, and payments run on SOC 2 Type II / PCI DSS Level 1 certified providers. Gramm security documents are available during procurement review.
Encryption
TLS enforced in transit. Encrypted storage at rest. API keys stored as hashes, never plaintext.
Access controls
Protected routes require authentication. Service-level access restricted to backend API routes only.
Data handling
Forecasts are precomputed outputs, no ad hoc inference triggered by customer API calls. Your query patterns are not stored.
Data residency
US-only. Customer accounts, API keys, and forecast metadata are stored on Supabase (AWS US regions) and served via Vercel's North American edge. No data leaves US infrastructure.
Procurement documents
MSA, DPA, subprocessor list, SIG-lite / CAIQ, and incident-response policy sent within 2 business days of a signed NDA. Redlines welcome on MSA and DPA.
Review materials
One review path for security, SLA, and contracting.
Enterprise review should not require buyers to reconcile separate stories. Trust, service levels, procurement, and onboarding material stay linked from one place.
Infrastructure providers, encryption, access controls, and available security materials.
Support tiers, availability targets, incident communication, and Enterprise terms.
Vendor review sequence, required inputs, documents, and response expectations.
SSO, custom delivery, negotiated SLA, onboarding, and named engineering contact.
Ready to evaluate?
Start with the public benchmark. If the numbers look relevant, we'll run a backtest for your market.