Install Jentic One Beta

Connect the Swagger Internal Transfer request - OpenAPI 3.0 to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Swagger Internal Transfer request - OpenAPI 3.0, 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%2Fmypuma.net%2Fmypuma" | sh

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%2Fmypuma.net%2Fmypuma" | 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 Swagger Internal Transfer request - OpenAPI 3.0 API.

Exchange a client_id and client_secret for a bearer access_token with its expires_in value through POST /auth/token

Submit a batch of internal transfer requests, each tying an so_number and article to a factory_code, through POST /chatbot/internal-transfer

Record who changed a transfer with the updated_by email and updated_at date on each item

Read field-level validation errors keyed by path, such as payload.0.season, to fix a rejected batch

GET STARTED

Start building with Swagger Internal Transfer request - OpenAPI 3.0 API

Explore with Jentic One

View OpenAPI Document

★ Agent-submitted factory transfers through Jentic

A sourcing coordinator asks an agent, connected through Jentic, to move several sales order lines to a different factory. The agent builds one array item per line with so_number, article, season, factory_code, purchase_requisition, request_id, and the coordinator's updated_by email, then submits the batch in a single call and reports the status and message from the response.

Call POST /chatbot/internal-transfer with an array containing one item: request_id='2945245', purchase_requisition='3004718909', season='202611', article='406887 05', so_number='0123296842', factory_code='FCNRF', updated_at='2026-11-09', updated_by='coordinator@example.com'

Fixing a rejected transfer batch

When a batch fails, the service returns HTTP 422 with an error and a details array, where each entry names the failing field by path, such as payload.1.factory_code, and gives a readable message. An agent reads those paths, corrects the matching items, for example padding a season to six digits ending in 11 or 21, and resubmits only once the batch is clean.

Submit the batch to POST /chatbot/internal-transfer, and on a 422 response read each details[].field and details[].error, correct the named items, and resubmit

Token handling for the sourcing service

Calls to the transfer endpoint carry a bearer access token. The token operation takes a client_id and client_secret and returns an access_token with token_type Bearer and an expires_in value, which the caller reuses until it expires instead of requesting a new token for every batch.

Call POST /auth/token with client_id and client_secret, store access_token and expires_in, and use the token on POST /chatbot/internal-transfer until it expires

Key Endpoints

2 endpoints — the puma internal transfer request api submits batches of internal transfer requests to puma's sourcing automation service, moving a sales order line to a factory.

METHOD

PATH

DESCRIPTION

POST

/chatbot/internal-transfer

Submit internal transfer requests

POST

/auth/token

Request an access token

POST

/chatbot/internal-transfer

Submit internal transfer requests

POST

/auth/token

Request an access token

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring this API by hand means exchanging a client_id and client_secret for a bearer token, tracking expires_in, choosing the production or staging host, and matching the season, article, and so_number patterns. Through Jentic you install once, import it from the API Directory, store the client credentials once, and your agent calls it.

Permission scoping

This API carries the sales order and factory inside the request body, so rules bound which operations your agent may call, not which factory or order. Limit the agent to the operations it needs, such as submitting transfer requests.

Credential isolation

Your PUMA client secret and bearer token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'submit an internal transfer request' or 'move a sales order to a factory', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Swagger Internal Transfer request - OpenAPI 3.0 API through Jentic.

What authentication does the PUMA Internal Transfer Request API use?

Per its OpenAPI spec, the API declares a JWT bearer scheme, sent as Authorization: Bearer. POST /auth/token takes a client_id and client_secret in the request body and returns an access_token, a token_type of Bearer, and expires_in. Through Jentic, the client secret and token are stored once by your own Jentic One instance and injected at call time.

What does each internal transfer request contain?

POST /chatbot/internal-transfer takes an array, so one call can carry several requests. Each item has request_id, purchase_requisition, season, article, so_number, factory_code, updated_at, and updated_by. The spec patterns require season to be six digits, so_number to be digits only, and article to end in a space and two digits, as in 406887 05, and updated_by must be an email address.

What happens when a transfer request fails validation?

The service returns HTTP 422 with an error string and a details array. Each detail gives a field path such as payload.0.so_number and a message, for example that the season must end in 11 for spring or 21 for autumn, or that factory_code must be a non-empty string.

What are the rate limits for the PUMA Internal Transfer Request API?

The OpenAPI spec does not specify rate limits. It lists a production host at sourcing-automation.pdss.mypuma.net and a staging host at sourcing-automation.pdssstage.mypuma.net; test batches against staging and check with the PUMA sourcing team that issued your client credentials for current limits.

How do I submit a transfer request through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import the API from the API Directory, and store your client credentials once. Your agent searches for 'submit an internal transfer request', gets the transfer operation with its input schema, and calls POST /chatbot/internal-transfer with the batch. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the PUMA Internal Transfer Request API?

Yes. A rule can allow POST /chatbot/internal-transfer and leave out POST /auth/token, so your Jentic One instance handles the token and the agent only submits transfers. Because the factory and sales order travel in the request body, a rule cannot restrict which factory_code the agent sends.

Mypuma Swagger Internal Transfer request - OpenAPI 3.0

AI ReadinessFoundational (C)57/100

See full scorecard

Community OpenAPI document · agent-readyE CommerceOrder Managementbearer2 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Submit validated batches of PUMA internal transfer requests that move a sales order article to a factory code, after exchanging client credentials for a bearer token.

Use for: Submit an internal transfer for sales order 0123296842 to factory FCNRF, Request an access token for the sourcing automation service, Send a batch of transfer requests for the spring season, Check why a transfer batch failed validation

Not supported: Does not create or look up sales orders, track shipments, or report stock levels. Use for submitting PUMA internal transfer requests only.

The PUMA Internal Transfer Request API submits batches of internal transfer requests to PUMA's sourcing automation service, moving a sales order line to a factory. Each request in the array carries a request_id, purchase_requisition, season, article, so_number, factory_code, updated_at, and updated_by. The service validates every item and returns field-level errors, such as an so_number that is not all digits or a season that does not end in 11 for spring or 21 for autumn. A separate token operation exchanges a client_id and client_secret for a bearer access token.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

23%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

20%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

50%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

75%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: FSignals: 1

38%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Swagger Internal Transfer request - OpenAPI 3.0 to your agent

Capabilities

Start building with Swagger Internal Transfer request - OpenAPI 3.0 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Mypuma Swagger Internal Transfer request - OpenAPI 3.0

Jentic AI Readiness Score

Swagger Internal Transfer request - OpenAPI 3.0

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness