Developer ToolsProject ManagementapiKey, bearer256 EndpointsREST
For Agents
Programmatically check_permission_retrieve, day_create. Covers 256 operations with apiKey, bearer authentication.
Use for: I need to check_permission_retrieve, I want to day_create, Search for day_list, Find all day_retrieve
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Self hosted FLOSS workout and fitness tracker. The API exposes 256 endpoints secured with apiKey, bearer authentication.
Install Jentic One Beta
Connect the wger to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the wger, 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%2Fwger.de%2Fwger" | 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%2Fwger.de%2Fwger" | 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 wger API.
check_permission_retrieve
day_create
day_list
day_retrieve
day_update
day_partial_update
day_destroy
Use Cases
Patterns agents use wger API for, with concrete tasks.
★ Developer Tools Operations
Use the wger to perform developer tools operations programmatically. The API provides 256 endpoints covering core functionality including check_permission_retrieve, day_create, day_list.
Call GET /api/v2/check-permission/ to check_permission_retrieve
Automated Check Permission Management
Automate check permission operations by combining multiple wger endpoints. Agents can day_create and then day_list in a single workflow.
Call POST /api/v2/day/ to day_create, then verify the result
AI Agent Integration via Jentic
AI agents discover and call wger 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, bearer tokens manually.
Search Jentic for 'check_permission_retrieve', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
256 endpoints — self hosted floss workout and fitness tracker.
METHOD
PATH
DESCRIPTION
GET
/api/v2/check-permission/
check_permission_retrieve
POST
/api/v2/day/
day_create
GET
/api/v2/day/
day_list
GET
/api/v2/day/{id}/
day_retrieve
PUT
/api/v2/day/{id}/
day_update
PATCH
/api/v2/day/{id}/
day_partial_update
DELETE
/api/v2/day/{id}/
day_destroy
GET
/api/v2/deletion-log/
deletion_log_list
GET
/api/v2/check-permission/
check_permission_retrieve
POST
/api/v2/day/
day_create
GET
/api/v2/day/
day_list
GET
/api/v2/day/{id}/
day_retrieve
PUT
/api/v2/day/{id}/
day_update
PATCH
/api/v2/day/{id}/
day_partial_update
DELETE
/api/v2/day/{id}/
day_destroy
GET
/api/v2/deletion-log/
deletion_log_list
Jentic AI Readiness Score
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.
W
wger
- Foundational (D)44/100
66
Foundational Compliance57
Developer Experience & Jentic Compatibility32
AI-Readiness & Agent Experience43
Agent Usability58
Security36
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
66
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: BSignals: 4
65%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
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.
57
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C+Signals: 4
5%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
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.
32
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
29%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
43
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: D-Signals: 1
43%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
58
Security
Trust, risk posture, and security compliance.
Grade: C+Signals: 1
58%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
36
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: FSignals: 1
36%
Descriptive Richness
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>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the wger API by hand means picking between its token header auth and JWT bearer auth and handling retries yourself across its large v2 surface. Through Jentic you install once, import wger from the API Directory, store the token once, and your agent calls it.
Permission scoping
wger puts the resource id in the URL path (/api/v2/day/{id}/), so a rule can pin your agent to reading a training day and nothing else. You choose the operations it may call, so destructive ones like deleting or overwriting a day with PUT or DELETE are not included unless you add them.
Credential isolation
Your wger 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 'check a permission' or 'read a training day', and Jentic returns the matching wger 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.
FAQs
Specific to using wger API through Jentic.
What authentication does the wger use?
The wger uses apiKey, bearer authentication. 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 check_permission_retrieve with the wger?
Yes. Use the GET /api/v2/check-permission/ endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the wger?
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 check_permission_retrieve through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'check_permission_retrieve'. Jentic returns the matching wger operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the wger have?
The wger exposes 256 endpoints covering check permission, day, deletion log operations.
Can I limit what my agent is allowed to do with the wger API?
Yes. Because you run Jentic One yourself, your own rules decide which wger operations and credentials the agent may use. wger puts the resource id in the URL path, such as /api/v2/day/{id}/, so a rule can pin the agent to reading a single training day and nothing else. You pick the operations it may call, so destructive ones like overwriting a day with PUT or deleting it with DELETE stay off limits unless you add them.
GET STARTED