Labelbox Foundry API

Name: Labelbox Foundry API
Brand: Labelbox Foundry API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAI/MLMl Inferencebearer3 EndpointsREST

For Agents

Run Labelbox Foundry model predictions: create a prediction job for a Foundry app, fetch results by ID, and search prior prediction jobs.

Install Jentic One Beta

Connect the Labelbox Foundry API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Labelbox Foundry 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Labelbox Foundry API.

Create a prediction job for a Foundry app via POST /foundry-app/{appId}/predict with the input data and run parameters

Retrieve completed prediction results by job ID via GET /foundry-app/prediction/{id}

Search and filter prior prediction jobs for a Foundry app via POST /foundry-app/{appId}/predictions

GET STARTED

Start building with Labelbox Foundry API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Labelbox Foundry API for, with concrete tasks.

★ Image Classification at Scale

Run a packaged Foundry vision model over a batch of images. POST /foundry-app/{appId}/predict creates the job with input data and parameters; GET /foundry-app/prediction/{id} polls for completion and returns the predictions. This avoids hosting and operating the model directly while still benefitting from a stable inference contract.

POST /foundry-app/{appId}/predict with the image batch, then poll GET /foundry-app/prediction/{id} until status is complete and read the labels.

Document Extraction Workflow

Use a Foundry document-understanding app to extract structured fields from PDFs. The agent submits each document to POST /foundry-app/{appId}/predict, polls GET /foundry-app/prediction/{id} for the structured output, and writes the resulting fields into downstream systems. POST /foundry-app/{appId}/predictions can search past runs to avoid duplicate processing.

POST /foundry-app/{appId}/predict with the PDF reference, poll GET /foundry-app/prediction/{id}, and write the extracted fields into the data warehouse.

Audit Trail of Past Predictions

Maintain an audit trail of model predictions for compliance and debugging. POST /foundry-app/{appId}/predictions searches prior prediction jobs for the app, returning IDs that can be fetched in detail via GET /foundry-app/prediction/{id}. This supports investigation when downstream systems flag anomalies.

POST /foundry-app/{appId}/predictions filtered to the past 24 hours and emit a list of recent run IDs into the audit log.

AI Agent ML Operator

An agent in an ML-ops chat client triggers prediction jobs, polls results, and surfaces anomalies on instruction. Through Jentic, the agent calls Labelbox Foundry by intent without storing the bearer token in the agent runtime.

On 'classify these 200 images with the product-category model', POST /foundry-app/{appId}/predict with the image references and report back the IDs and statuses.

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for labelbox foundry api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/foundry-app/{appId}/predict

Create a prediction job

GET

/foundry-app/prediction/{id}

Get prediction results

POST

/foundry-app/{appId}/predictions

Search prediction jobs

POST

/foundry-app/{appId}/predict

Create a prediction job

GET

/foundry-app/prediction/{id}

Get prediction results

POST

/foundry-app/{appId}/predictions

Search prediction jobs

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Labelbox bearer tokens are stored encrypted in the Jentic MAXsystem vault. Jentic injects the Authorization header at execution time so the agent runtime never holds the raw token.

Intent-based discovery

Agents search by intent (e.g. 'run a Labelbox Foundry prediction') and Jentic returns the matching Foundry operation with its input schema.

Time to first call

Direct integration: half a day for auth, polling, and result handling. Through Jentic: under 30 minutes — search, load, execute.

FAQs

Specific to using Labelbox Foundry API through Jentic.

Why is there no official OpenAPI spec for Labelbox Foundry API?

Labelbox documents Foundry on docs.labelbox.com but does not publish a canonical OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Labelbox Foundry API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Labelbox Foundry API use?

The Foundry API uses HTTP bearer authentication: every request needs an Authorization header with a Labelbox-issued API key. Through Jentic, the key is stored encrypted in the MAXsystem vault and injected per request.

Can I run a prediction job with the Labelbox Foundry API?

Yes. POST /foundry-app/{appId}/predict creates a prediction job for a Foundry app with the input data and run parameters; GET /foundry-app/prediction/{id} returns the result once the job completes.

How do I retrieve prediction results through Jentic?

Search Jentic for 'get Labelbox Foundry prediction results'. Jentic returns GET /foundry-app/prediction/{id} with its schema. Provide the prediction ID and Jentic executes the call using your stored bearer token.

What rate limits apply to the Labelbox Foundry API?

Per-account rate limits aren't exposed in the public spec; Foundry pricing and concurrency are tied to your Labelbox plan. Refer to docs.labelbox.com or your Labelbox account team for current ceilings before scaling agent workloads.

Can I search prior Foundry prediction jobs?

Yes. POST /foundry-app/{appId}/predictions searches prior prediction jobs for a given Foundry app, which is useful for building audit trails, deduplicating runs, and debugging anomalous results.

Labelbox Foundry API

Connect the Labelbox Foundry API to your agent

Capabilities

Start building with Labelbox Foundry API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs