Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ballsportdirekt Spontent 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%2Fswaggerhub.zeyos%2Fballsportdirekt-spontent-api" | 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%2Fswaggerhub.zeyos%2Fballsportdirekt-spontent-api" | 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 Ballsportdirekt Spontent API.
Get Items
Create Order
Cancel Order
Query and filter Ballsportdirekt Spontent API records by parameters
GET STARTED
For Agents
Programmatically get items, get stock. Covers 5 operations.
Use for: I need to items, I want to stock, Search for order, Find all order status
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Ballsportdirekt Spontent API. The API exposes 5 endpoints.
Monitor Ballsportdirekt Spontent API operational status and events
Patterns agents use Ballsportdirekt Spontent API for, with concrete tasks.
★ Developer Tools Operations
Use the Ballsportdirekt Spontent API to perform developer tools operations programmatically. The API provides 5 endpoints covering core functionality including get items, get stock, create order.
Call GET /items to get items
Automated items Management
Automate items operations by combining multiple Ballsportdirekt Spontent API endpoints. Agents can get stock and then create order in a single workflow.
Call GET /stock to get stock, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Ballsportdirekt Spontent 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 none tokens manually.
Search Jentic for 'get items', load the operation schema, and execute with Jentic-managed credentials
5 endpoints — ballsportdirekt spontent api.
METHOD
PATH
DESCRIPTION
/items
Get Items
/stock
Get Stock
/order
Create Order
/order/{ID}
Get Order Status
/order/{ID}
Cancel Order
/items
Get Items
/stock
Get Stock
/order
Create Order
/order/{ID}
Get Order Status
/order/{ID}
Cancel Order
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Ballsportdirekt Spontent API by hand means coding its item, stock, and order calls against the ZeyOS cloud host and shaping each order payload yourself. Through Jentic you install once, import the Ballsportdirekt Spontent API from the API Directory, and your agent calls it.
Permission scoping
The Spontent API puts the order id in the URL path (/order/{ID}), so a rule can pin your agent to one order: it can read that order and nothing else. You choose the operations it may call, so destructive ones like deleting an order are not included unless you add them.
Credential isolation
Any credential you configure for the Ballsportdirekt Spontent API 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 items' or 'place an order', and Jentic returns the matching Ballsportdirekt Spontent 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.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Specific to using Ballsportdirekt Spontent API through Jentic.
What authentication does the Ballsportdirekt Spontent API use?
The Ballsportdirekt Spontent API uses no 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 get items with the Ballsportdirekt Spontent API?
Yes. Use the GET /items endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Ballsportdirekt Spontent 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 get items through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get items'. Jentic returns the matching Ballsportdirekt Spontent API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Ballsportdirekt Spontent API have?
The Ballsportdirekt Spontent API exposes 5 endpoints covering items, order, stock operations.
Can I limit what my agent is allowed to do with the Ballsportdirekt Spontent API?
Yes. Because you run Jentic One yourself, your own rules decide which of the Ballsportdirekt Spontent API operations your agent may call, so you can grant read-only access to GET /items and GET /stock while withholding PUT /order and DELETE /order/{ID}. Since the order id sits in the URL path at GET /order/{ID}, you can pin the agent to a single order and let it read that one and nothing else. Destructive calls such as cancelling an order are never available unless you explicitly add them. Any credential you configure is held by your own instance and injected only at execution time.