Srpnet SRP Energy API
59
AI ReadinessFoundational (C+)59/100
Official vendor OpenAPI document · agent-readyPaymentsPayment ProcessingapiKey3 EndpointsREST
For Agents
Programmatically authenticate user, get xsrf token. Covers 3 operations with apiKey authentication.
Use for: I need to authenticate user, I want to xsrf token, Search for hourly usage detail, List all records from SRP Energy API
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
API for accessing Salt River Project (SRP) energy usage data, including hourly consumption details and billing information. The API exposes 3 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the SRP Energy API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SRP Energy API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsrpnet.com%2Fsrpnet" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsrpnet.com%2Fsrpnet" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with SRP Energy API.
Authenticate user
Get XSRF token
Integrate SRP Energy API into automated workflows
Query and filter SRP Energy API records by parameters
Monitor SRP Energy API operational status and events
Use Cases
Patterns agents use SRP Energy API for, with concrete tasks.
★ Payments Operations
Use the SRP Energy API to perform payments operations programmatically. The API provides 3 endpoints covering core functionality including authenticate user, get xsrf token, get hourly usage detail.
Call POST /login/authorize to authenticate user
Automated Authentication Management
Automate authentication operations by combining multiple SRP Energy API endpoints. Agents can get xsrf token and then get hourly usage detail in a single workflow.
Call GET /login/authorize to get xsrf token, then verify the result
AI Agent Integration via Jentic
AI agents discover and call SRP Energy API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'authenticate user', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
3 endpoints — api for accessing salt river project (srp) energy usage data, including hourly consumption details and billing information.
METHOD
PATH
DESCRIPTION
POST
/login/authorize
Authenticate user
GET
/login/authorize
Get XSRF token
GET
/usage/hourlydetail
Get hourly usage detail
POST
/login/authorize
Authenticate user
GET
/login/authorize
Get XSRF token
GET
/usage/hourlydetail
Get hourly usage detail
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
S
SRP Energy API
- Foundational (C+)59/100
85
Foundational Compliance37
Developer Experience & Jentic Compatibility56
AI-Readiness & Agent Experience94
Agent Usability50
Security71
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
85
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
42%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
37
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: FSignals: 4
5%
Example Density
How richly the API is illustrated with examples.
0%
Example Validity
Percentage of examples that conform to their schemas.
42%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
56
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
62%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
60%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
71
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
71%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the SRP Energy API by hand means authorizing against myaccount.srpnet.com/myaccountapi/api and carrying its token into each usage call yourself. Through Jentic you install once, import the SRP Energy API from the API Directory, store the credential once, and your agent calls it.
Permission scoping
You can limit the agent to the operations it needs, such as authorizing and reading hourly usage detail, so it retrieves account usage and does nothing beyond the operations you allow.
Credential isolation
Your SRP Energy credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get my hourly energy usage', and Jentic returns the matching SRP Energy API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
FAQs
Specific to using SRP Energy API through Jentic.
What authentication does the SRP Energy API use?
The SRP Energy API uses an API key passed in the `x-xsrf-token` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I authenticate user with the SRP Energy API?
Yes. Use the POST /login/authorize endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SRP Energy API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I authenticate user through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'authenticate user'. Jentic returns the matching SRP Energy API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the SRP Energy API have?
The SRP Energy API exposes 3 endpoints covering authentication, usage operations.
Can I limit what my agent is allowed to do with the SRP Energy API?
Yes. Because Jentic One is self-hosted, you set the rules that decide which SRP Energy API operations and credentials your agent may use. You can allow it to authenticate and read hourly usage detail through GET /usage/hourlydetail while withholding any other endpoint, so it retrieves account usage and does nothing beyond what you permit. Your SRP Energy credential is stored encrypted by your own instance and injected only when an allowed call runs.
GET STARTED