Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the FORTNITE REST 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%2Fskynewz-api-fortnite.herokuapp.com%2Fskynewz-api-fortnite-herokuapp" | 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%2Fskynewz-api-fortnite.herokuapp.com%2Fskynewz-api-fortnite-herokuapp" | 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 FORTNITE REST API.
Get Fortnite game status
Manage developer tools data programmatically
Integrate FORTNITE REST API into automated workflows
Query and filter FORTNITE REST API records by parameters
Monitor FORTNITE REST API operational status and events
GET STARTED
Patterns agents use FORTNITE REST API for, with concrete tasks.
★ Developer Tools Operations
Use the FORTNITE REST API to perform developer tools operations programmatically. The API provides 9 endpoints covering core functionality including get fortnite game status, get fortnite news, get a bearer token.
Call GET /check to get fortnite game status
Automated Security Management
Automate security operations by combining multiple FORTNITE REST API endpoints. Agents can get fortnite news and then get a bearer token in a single workflow.
Call GET /news to get fortnite news, then verify the result
AI Agent Integration via Jentic
AI agents discover and call FORTNITE REST 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 apiKey tokens manually.
Search Jentic for 'get fortnite game status', load the operation schema, and execute with Jentic-managed credentials
9 endpoints — rest api about fortnite game.
METHOD
PATH
DESCRIPTION
/check
Get Fortnite game status
/news
Get Fortnite News
/oauth/token
Get a Bearer token
/pve/info
Get Fortnite PVE Info (storm, etc)
/pve/user/{username}
Get PVE Stat by given username
/stats/id/{plateform}/{id}
Get user's stats by user id
/stats/{plateform}/{username}
Get user's stats by username
/store
Get Fortnite Store
/check
Get Fortnite game status
/news
Get Fortnite News
/oauth/token
Get a Bearer token
/pve/info
Get Fortnite PVE Info (storm, etc)
/pve/user/{username}
Get PVE Stat by given username
/stats/id/{plateform}/{id}
Get user's stats by user id
/stats/{plateform}/{username}
Get user's stats by username
/store
Get Fortnite Store
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the FORTNITE REST API by hand means sending an Authorization header token to the skynewz-api-fortnite.herokuapp.com host and handling the stats, PvE, and store calls yourself. Through Jentic you install once, import the FORTNITE REST API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
This API puts the player username and id in the URL path (/stats/{plateform}/{username} and /pve/user/{username}), so a rule can pin your agent to specific player lookups. You choose the operations it may call, so if you only grant stats reads, the news and store operations are not included unless you add them.
Credential isolation
Your FORTNITE REST API key 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 'get a player's stats' or 'fetch the item store', and Jentic returns the matching FORTNITE REST 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.
Specific to using FORTNITE REST API through Jentic.
What authentication does the FORTNITE REST API use?
The FORTNITE REST API uses an API key passed 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 get fortnite game status with the FORTNITE REST API?
Yes. Use the GET /check endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the FORTNITE REST 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 fortnite game status through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get fortnite game status'. Jentic returns the matching FORTNITE REST API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the FORTNITE REST API have?
The FORTNITE REST API exposes 9 endpoints covering security, user, stats operations.
Can I limit what my agent is allowed to do with the FORTNITE REST API?
Yes. Jentic One runs self-hosted, so your own rules decide which FORTNITE REST API operations and credentials your agent may use. You pick the operations it can call, so granting only the stats reads such as GET /stats/{plateform}/{username} and GET /pve/user/{username} leaves the news and store endpoints off-limits until you add them. Because the player username and id sit in the URL path, you can pin the agent to specific player lookups rather than open-ended access.
For Agents
Programmatically get fortnite game status, get fortnite news. Covers 9 operations with apiKey authentication.
Use for: I need to fortnite game status, I want to fortnite news, Search for a bearer token, Find all fortnite pve info (storm, etc)
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
REST API about Fortnite game. The API exposes 9 endpoints secured with apiKey authentication.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>