canonical: https://jentic.com/apis/srpnet.com/srpnet

# Srpnet SRP Energy API

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.

## For AI agents

Programmatically authenticate user, get xsrf token. Covers 3 operations with apiKey authentication.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'authenticate user', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/login/authorize` | Authenticate user |
| GET | `/login/authorize` | Get XSRF token |
| GET | `/usage/hourlydetail` | Get hourly usage detail |

## Key resources

- **Authentication** — Authentication and authorization endpoints
- **Usage** — Energy usage data endpoints

## AI readiness

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.

- **Score:** 59 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 85 / 100
  - Developer Experience & Jentic Compatibility: 37 / 100
  - AI-Readiness & Agent Experience: 56 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 71 / 100
- **View full report:** https://jentic.com/apis/srpnet.com/srpnet/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### 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.