For Agents
Programmatically generate a new session, generate an access token. Covers 32 operations with basic, bearer authentication.
Use for: I need to generate a new session, I want to generate an access token, Search for customers, Find all a customer
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
Slope API provides B2B payment infrastructure including order management, customer credit, and payment processing. The API exposes 32 endpoints secured with basic, bearer authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Slope 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%2Fslopepay.com%2Fslopepay" | 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%2Fslopepay.com%2Fslopepay" | 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 Slope API.
Generate a new session
List customers
Get a customer
Query and filter Slope API records by parameters
Monitor Slope API operational status and events
Patterns agents use Slope API for, with concrete tasks.
★ Payments Operations
Use the Slope API to perform payments operations programmatically. The API provides 32 endpoints covering core functionality including generate a new session, generate an access token, list customers.
Call POST /auth/session to generate a new session
Automated Auth Management
Automate auth operations by combining multiple Slope API endpoints. Agents can generate an access token and then list customers in a single workflow.
Call POST /auth/token to generate an access token, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Slope 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 basic, bearer tokens manually.
Search Jentic for 'generate a new session', load the operation schema, and execute with Jentic-managed credentials
32 endpoints — slope api provides b2b payment infrastructure including order management, customer credit, and payment processing.
METHOD
PATH
DESCRIPTION
/auth/session
Generate a new session
/auth/token
Generate an access token
/customers
List customers
/customers/{id}
Get a customer
/customers/{customerId}/credit
Get a customer's credit
/customers/{customerId}/orders
List customer's orders
/customers/{customerId}/payment-methods
List customer's payment methods
/customers/validate-metadata
Validate metadata
/auth/session
Generate a new session
/auth/token
Generate an access token
/customers
List customers
/customers/{id}
Get a customer
/customers/{customerId}/credit
Get a customer's credit
/customers/{customerId}/orders
List customer's orders
/customers/{customerId}/payment-methods
List customer's payment methods
/customers/validate-metadata
Validate metadata
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Slope by hand means implementing its basic and bearer auth against api.slopepay.com, minting session tokens, and handling retries yourself. Through Jentic you install once, import the Slope API from the API Directory, store the credential once, and your agent calls it.
Permission scoping
Slope puts the customer id in the URL path (/customers/{customerId}/...), so a rule can pin your agent to one customer: it can read that customer's credit, orders, and payment methods and nothing else. You choose the operations it may call, so writes like metadata validation are not included unless you add them.
Credential isolation
Your Slope 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 'list a customer's orders' or 'check a customer's credit', and Jentic returns the matching Slope 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 Slope API through Jentic.
What authentication does the Slope API use?
The Slope API uses basic, bearer authentication. 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 generate a new session with the Slope API?
Yes. Use the POST /auth/session endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Slope 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 generate a new session through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'generate a new session'. Jentic returns the matching Slope API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Slope API have?
The Slope API exposes 32 endpoints covering auth, customers, files operations.
Can I limit what my agent is allowed to do with the Slope API?
Yes. Because you run Jentic One yourself, your own rules decide which Slope operations and credentials the agent may use, and the Slope API places the customer id in the URL path (/customers/{customerId}/...), so a rule can pin the agent to a single customer. Scoped that way, it can read that customer's credit, orders, and payment methods and nothing else. You also choose which operations are exposed, so write actions like POST /customers/validate-metadata are excluded unless you add them.
GET STARTED