canonical: https://jentic.com/apis/wikipathways.org/wikipathways # WikiPathways Webservices wikipathways.org/main version 1.0. The API exposes 27 endpoints. ## For AI agents Programmatically access WikiPathways Webservices resources. Covers 27 operations. ## Scope Does not handle payments, communications, or crm - use for productivity only. ## Capabilities - Access WikiPathways Webservices resources via REST API - Manage productivity data programmatically - Integrate WikiPathways Webservices into automated workflows - Query and filter WikiPathways Webservices records by parameters - Monitor WikiPathways Webservices operational status and events ## Use cases ### Productivity Operations The API provides 27 endpoints for productivity operations. Example prompt: Execute a primary operation against the WikiPathways Webservices ### Data Retrieval and Monitoring Query WikiPathways Webservices resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed. Example prompt: Poll the primary WikiPathways Webservices endpoint, compare response to last known state, and alert if changed ### AI Agent Integration via Jentic AI agents discover and call WikiPathways Webservices 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 none tokens manually. Example prompt: Search Jentic for 'wikipathways webservices', load the operation schema, and execute with Jentic-managed credentials ## Key resources - **Createpathway** — Operations for createPathway - **Findinteractions** — Operations for findInteractions - **Findpathwaysbyliterature** — Operations for findPathwaysByLiterature - **Findpathwaysbytext** — Operations for findPathwaysByText - **Findpathwaysbyxref** — Operations for findPathwaysByXref ## AI readiness 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. - **Score:** 30 / 100 - **Maturity:** Non-Ready - **Dimensions:** - Foundational Compliance: 73 / 100 - Developer Experience & Jentic Compatibility: 56 / 100 - AI-Readiness & Agent Experience: 11 / 100 - Agent Usability: 94 / 100 - Security: 100 / 100 - AI Discoverability: 40 / 100 - **View full report:** https://jentic.com/apis/wikipathways.org/wikipathways/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring WikiPathways Webservices by hand means targeting webservice.wikipathways.org, choosing the right query operation, and parsing its pathway responses yourself. Through Jentic you install once, import WikiPathways Webservices from the API Directory, store the connection once, and your agent calls it. - **Permission scoping:** WikiPathways Webservices is a read query service that takes its target in the request, so limit the agent to the operations it needs, such as listing or fetching pathways. You choose the operations it may call, so nothing beyond that set runs unless you add it. - **Credential handling:** Any WikiPathways connection detail 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. - **Discovery method:** Agents search Jentic by intent such as 'find a biological pathway', and Jentic returns the matching WikiPathways operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Asana** — Alternative productivity API - **Monday** — Alternative productivity API - **Clickup** — Complementary productivity API ## FAQ ### What authentication does the WikiPathways Webservices use? The WikiPathways Webservices uses no 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. ### What are the rate limits for the WikiPathways Webservices? 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 use wikipathways webservices through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'use wikipathways webservices'. Jentic returns the matching WikiPathways Webservices operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the WikiPathways Webservices have? The WikiPathways Webservices exposes 27 endpoints covering createpathway, findinteractions, findpathwaysbyliterature operations. ### Does the WikiPathways Webservices support pagination? Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically. ### Can I limit what my agent is allowed to do with the WikiPathways API? Yes. WikiPathways is a read-only query service, so in your self-hosted Jentic One instance you decide which operations the agent may call and which connection details it may use. You can restrict it to just the queries it needs, such as findPathwaysByText, findPathwaysByXref, findInteractions, or fetching a pathway, and leave out anything else like createPathway. Because your own rules define that operation set, nothing outside it runs unless you add it.