canonical: https://jentic.com/apis/pulpminer.com/pulpminer # PulpMiner API PulpMiner is a tool that lets you convert any webpage to a realtime JSON API. Access your data via simple API requests. The API exposes 2 endpoints secured with apiKey authentication. ## For AI agents Programmatically retrieve dynamic API data, retrieve static API data. Covers 2 operations with apiKey authentication. ## Scope Does not handle payments, communications, or crm - use for developer tools only. ## Capabilities - Retrieve dynamic API data - Access PulpMiner API resources via REST API - Access PulpMiner API resources via REST API ## Use cases ### Developer Tools Operations Use the PulpMiner API to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including retrieve dynamic API data, retrieve static API data. Example prompt: Call POST `/external/{apiId}` to retrieve dynamic API data ### Data Retrieval and Monitoring Query PulpMiner API endpoints to retrieve structured data for monitoring, reporting, or downstream processing. The API returns JSON responses that agents can parse directly, enabling automated data collection workflows without manual intervention. Example prompt: Query the PulpMiner API API to retrieve current data and verify the response contains expected fields ### AI Agent Integration via Jentic AI agents discover and call PulpMiner 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. Example prompt: Search Jentic for 'retrieve dynamic API data', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/external/{apiId}` | Retrieve dynamic API data | | GET | `/external/{apiId}` | Retrieve static API data | ## Key resources - **Endpoints** — API endpoint operations ## 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:** 68 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 60 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 63 / 100 - **View full report:** https://jentic.com/apis/pulpminer.com/pulpminer/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 the PulpMiner API by hand means setting your key in the apikey header and threading the apiId through each call yourself. Through Jentic you install once, import PulpMiner from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** PulpMiner puts the API id in the URL path (`/external/{apiId}`), so a rule can pin your agent to reading data from a specific configured API. You choose the operations it may call, so the POST that submits data is not included unless you add it. - **Credential handling:** Your PulpMiner 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. - **Discovery method:** Agents search Jentic by intent such as 'retrieve data for a configured API', and Jentic returns the matching PulpMiner operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Github** — Alternative developer tools API - **Gitlab** — Alternative developer tools API ## FAQ ### What authentication does the PulpMiner API use? The PulpMiner API uses an API key passed in the `apikey` 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 retrieve dynamic API data with the PulpMiner API? Yes. Use the POST `/external/{apiId}` endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the PulpMiner 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 retrieve dynamic API data through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieve dynamic API data'. Jentic returns the matching PulpMiner API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the PulpMiner API have? The PulpMiner API exposes 2 endpoints covering endpoints operations. ### Can I limit what my agent is allowed to do with the PulpMiner API? Yes. Jentic One is self-hosted, so your own rules decide which of the PulpMiner API's two operations your agent may call. Because PulpMiner puts the API id in the URL path (`/external/{apiId}`), you can pin the agent to reading data from a specific configured API, and you can allow only the GET that retrieves static data while withholding the POST that submits data. Your API key is stored once by your own instance and injected only when a permitted operation runs.