Seldon External API
Browse all Seldon APIsDeveloper ToolsSource Controlbearer2 EndpointsREST
For Agents
Programmatically predict, sendfeedback. Covers 2 operations with bearer authentication.
Use for: I need to predict, I want to sendfeedback, Get the current status of Seldon External API resources, List all records from Seldon External API
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
seldon.local/engine version 0.1. The API exposes 2 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Seldon External API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Seldon External 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%2Fseldon.local%2Fseldon-external-api" | 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%2Fseldon.local%2Fseldon-external-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.
Capabilities
What an agent can do with Seldon External API.
Predict
SendFeedback
Integrate Seldon External API into automated workflows
Query and filter Seldon External API records by parameters
Monitor Seldon External API operational status and events
Use Cases
Patterns agents use Seldon External API for, with concrete tasks.
★ Developer Tools Operations
Use the Seldon External API to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including predict, sendfeedback.
Call POST /seldon/{namespace}/{deployment}/api/v1.0/predictions to predict
Data Retrieval and Monitoring
Query Seldon External API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary Seldon External API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Seldon External 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 bearer tokens manually.
Search Jentic for 'predict', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
2 endpoints — seldon.
METHOD
PATH
DESCRIPTION
POST
/seldon/{namespace}/{deployment}/api/v1.0/predictions
Predict
POST
/seldon/{namespace}/{deployment}/api/v1.0/feedback
SendFeedback
POST
/seldon/{namespace}/{deployment}/api/v1.0/predictions
Predict
POST
/seldon/{namespace}/{deployment}/api/v1.0/feedback
SendFeedback
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Seldon External API engine by hand means supplying its bearer token, resolving the deployment {host} and {port} into the right base URL, and building each prediction and feedback request yourself. Through Jentic you install once, import Seldon External from the API Directory, store the token once, and your agent calls it.
Permission scoping
Seldon puts the namespace and deployment in the URL path (/seldon/{namespace}/{deployment}/...), so a rule can pin your agent to one deployment: it can send predictions and feedback there and nothing else. You choose the operations it may call, so feedback submission is not included unless you add it.
Credential isolation
Your Seldon token 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 'send a prediction request to a model' or 'submit feedback on a prediction', and Jentic returns the matching Seldon 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
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using Seldon External API through Jentic.
What authentication does the Seldon External API use?
The Seldon External API uses a Bearer token in the Authorization 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 predict with the Seldon External API?
Yes. Use the POST /seldon/{namespace}/{deployment}/api/v1.0/predictions endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Seldon External 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 predict through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'predict'. Jentic returns the matching Seldon External API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Seldon External API have?
The Seldon External API exposes 2 endpoints covering seldon operations.
Can I limit what my agent is allowed to do with the Seldon External API?
Yes. Because you run Jentic One yourself and write the rules that decide which operations and credentials your agent may use, you control exactly what it can call on the Seldon External API. Seldon places the namespace and deployment in the URL path, so a rule can pin the agent to a single deployment, and you choose whether it may send predictions, submit feedback, or both. If you only allow the predictions operation, the agent cannot post feedback, and it cannot touch any other deployment.
GET STARTED