---
title: "Neuralk Seldon API free inference"
description: "A finite allowance for new accounts; it does not recur."
canonical_url: "https://freeinferencing.com/provider/neuralk_seldon_api/"
md_url: "https://freeinferencing.com/provider/neuralk_seldon_api.md"
last_updated: "2026-09-19"
---

# Neuralk Seldon API

> A finite allowance for new accounts; it does not recur.

## Classification

- **Directory:** Current
- **Free access:** One-time trial
- **Status:** Current trial
- **Confidence:** High
- **Payment card:** No
- **Account:** Required
- **Equivalent paid value:** Not quantifiable
- **API endpoint:** `https://prediction.neuralk.ai/register`

## Models mentioned

- `seldon-flash`
- `seldon-small`
- `seldon-large`

## Limits and terms

```yaml
signup_credits: 50
rows_per_credit_approximate: 1000
maximum_rows_if_fully_consumed: 50000
recurrence: false
expiry: not_publicly_documented
```

## What happens to your prompts?

**Partially private.** Default predictions are memory-only and discarded, but optional upload mode retains datasets up to 90 days and public terms do not resolve training rights for every mode.

Privacy is audited separately from price. Review the current governing terms before sending sensitive or regulated data.

## Data governance and agreements

```yaml
data_governance:
  review_status: partial
  plan_scope: Default Seldon prediction requests plus optional upload mode.
  prompt_retention: Default prediction data is memory-only and discarded; upload
    mode persists data for a selected TTL.
  response_retention: Raw predictions are not stored in default mode.
  ordinary_logging: Metadata only in default mode, including request ID,
    timestamp, model, latency, credits, status, IP, and user agent.
  model_training: Public materials do not expressly resolve training rights for every mode.
  product_improvement: Not specifically documented for raw inference content.
  human_or_operator_access: Default mode leaves no persisted raw dataset; access
    controls for uploads are not fully public.
  subprocessors_and_routing: Processing occurs on Scaleway infrastructure in Paris without leaving the EU.
  deletion_controls: Default mode discards data; upload mode supports 1-, 7-, 30-,
    or 90-day TTLs and defaults to 90 days.
agreements:
  security_overview: https://www.neuralk.ai/data-security-overview
  upload_retention_docs: https://docs.neuralk.ai/getting_started/data_upload_retention.html
```

## Eligibility

```yaml
account_required: true
payment_method_required: not_explicitly_documented
```

## API compatibility and modalities

- **Compatibility:** Python Sdk Scikit Learn Style
- **Modalities:** Model inference


## Before you build with Neuralk Seldon API

### Read the classification narrowly

This record describes the bounded offer supported by evidence on 2026-09-19; it does not guarantee permanence, production suitability, uptime, latency, model quality, or access from every account and region. “One-time trial” should be interpreted together with the Current directory placement, High confidence, No payment-card status, and the plan-specific sources below.

### Resolve the live model route

The snapshot records 3 model IDs. Match the exact ID against the provider's current catalog before using it in code because zero-price routes, aliases, context limits, and feature support can rotate while an older documentation page remains online.

### Match the quota to the workload shape

Translate the allowance into peak requests per minute, input and output tokens, concurrency, retries, and every daily or monthly ceiling that applies to the intended account. The first limit reached by the workload is the practical ceiling. A large token pool can still fail interactive bursts, and a high request limit can still fail long-context work. Include tool calls and retry traffic, test the largest realistic payload, and treat research, experimental, and community access as conditional on their eligibility and fair-use terms.

### Preserve billing and privacy boundaries

The recorded payment-card requirement is No, and account access is required. Confirm both in the live signup flow, set provider-side budgets when charges are possible, and observe the balance or usage fields after a complete request. The prompt-handling classification is **Partially private** because Default predictions are memory-only and discarded, but optional upload mode retains datasets up to 90 days and public terms do not resolve training rights for every mode. Re-read the terms for the exact route and plan before sending sensitive, regulated, or proprietary content.

### Follow the evidence, then re-check it

This record links 6 first-party sources covering the offer, catalog, limits, pricing, terms, privacy, or adoption evidence available to the audit. Prefer the newest and most specific governing document or live catalog when sources disagree. A dated finding can become stale even when the page remains online, so retain the source and snapshot that supported the decision and submit a correction when a provider changes a material term.

### Plan fallback without policy drift

A fallback should preserve modality, context length, streaming, structured output, tools, safety controls, and data terms, not only API syntax. Decide which errors may retry, cap retry storms, and prevent an exhausted free route from silently switching to a billable model. Rotating aliases and free pools can change behavior without changing the endpoint, so retain the response model field and test at least one substitute route before the primary offer becomes unavailable.

### Monitor the offer as a dependency

Capture the model ID, response model, rate-limit headers, usage fields, latency, HTTP status, and provider request identifier. Watch authorization failure, quota exhaustion, catalog removal, policy revision, and balance movement as separate failure modes. Re-check the live catalog and governing sources on a schedule proportionate to the workload's importance, and keep an owner and exit path for any production dependency on volatile free capacity.

### Test one complete request before scaling

Start with the smallest permitted request using the exact credential, model ID, endpoint, region, and account type intended for deployment. Record the status, headers, usage fields, response model, latency, and dashboard balance movement. Then exercise an invalid model, quota exhaustion, or rate limit so failure is explicit and cannot silently switch to a paid route. Validate streaming, structured output, and tool calls separately because a free model can expose fewer features than its paid counterpart. Keep a budget ceiling outside the application whenever billing is possible, and do not send sensitive data until the observed route matches the reviewed agreement.

## Primary sources

- [Pricing and trial](https://www.neuralk.ai/pricing): Official Pricing
- [Seldon API is open](https://www.neuralk.ai/post/seldon-api-is-now-open-start-testing-for-free): Official Announcement
- [Quickstart](https://docs.neuralk.ai/getting_started/quickstart.html): Official Docs
- [Model FAQ](https://docs.neuralk.ai/getting_started/faq.html): Official Docs
- [Data Security Overview](https://www.neuralk.ai/data-security-overview): Official Security
- [Data upload and retention](https://docs.neuralk.ai/getting_started/data_upload_retention.html): Official Docs

## Sitemap

See the full [semantic sitemap](/sitemap.md) for every page and markdown mirror.