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
Install Jentic One Beta
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.
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" | shStep 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.
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
GET STARTED
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.
Monitor SRP Energy API operational status and events
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
3 endpoints — api for accessing salt river project (srp) energy usage data, including hourly consumption details and billing information.
METHOD
PATH
DESCRIPTION
/login/authorize
Authenticate user
/login/authorize
Get XSRF token
/usage/hourlydetail
Get hourly usage detail
/login/authorize
Authenticate user
/login/authorize
Get XSRF token
/usage/hourlydetail
Get hourly usage detail
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.
Alternatives and complements available in the Jentic catalogue.
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
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.