Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Article Rewriter and Article Extractor 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%2Fspinbot.net%2Fspinbot" | 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%2Fspinbot.net%2Fspinbot" | 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 Article Rewriter and Article Extractor API.
Return the user credit information.
Extracting the main article of the given URL.
Human readable auto rewrite your article.
Rewriting (spinning) your input article.
Generate Spintax format for the input article
GET STARTED
Patterns agents use Article Rewriter and Article Extractor API for, with concrete tasks.
★ Developer Tools Operations
Use the Article Rewriter and Article Extractor API to perform developer tools operations programmatically. The API provides 5 endpoints covering core functionality including return the user credit information., extracting the main article of the given url., human readable auto rewrite your article..
Call GET /api/acc to return the user credit information.
Automated article rewriter Management
Automate article rewriter operations by combining multiple Article Rewriter and Article Extractor API endpoints. Agents can extracting the main article of the given url. and then human readable auto rewrite your article. in a single workflow.
Call POST /api/article to extracting the main article of the given url., then verify the result
AI Agent Integration via Jentic
AI agents discover and call Article Rewriter and Article Extractor 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 'return the user credit information.', load the operation schema, and execute with Jentic-managed credentials
5 endpoints — spinbot.
METHOD
PATH
DESCRIPTION
/api/acc
Return the user credit information.
/api/article
Extracting the main article of the given URL.
/api/pretty-spinner
Human readable auto rewrite your article.
/api/spinner
Rewriting (spinning) your input article.
/api/spintax
Generate Spintax format for the input article
/api/acc
Return the user credit information.
/api/article
Extracting the main article of the given URL.
/api/pretty-spinner
Human readable auto rewrite your article.
/api/spinner
Rewriting (spinning) your input article.
/api/spintax
Generate Spintax format for the input article
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Spinbot Article Rewriter and Article Extractor API by hand means provisioning its API key, attaching it to every request, and pointing calls at the api.spinbot.net host yourself. Through Jentic you install once, import the Article Rewriter and Article Extractor API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
Spinbot takes its article text and options in the request body rather than as a resource in the URL path, so limit the agent to the operations it needs, such as spinning an article or extracting spintax. Naming operations, not a single article, is the honest boundary here.
Credential isolation
Your Spinbot 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 'rewrite an article' or 'check my credit balance', and Jentic returns the matching Article Rewriter and Article Extractor 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 Article Rewriter and Article Extractor API through Jentic.
What authentication does the Article Rewriter and Article Extractor API use?
The Article Rewriter and Article Extractor API uses an API key passed in the `key` query. 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 return the user credit information. with the Article Rewriter and Article Extractor API?
Yes. Use the GET /api/acc endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Article Rewriter and Article Extractor 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 return the user credit information. through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'return the user credit information.'. Jentic returns the matching Article Rewriter and Article Extractor API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Article Rewriter and Article Extractor API have?
The Article Rewriter and Article Extractor API exposes 5 endpoints covering article rewriter, article extractor operations.
Can I limit what my agent is allowed to do with the Spinbot Article Rewriter and Article Extractor API?
Yes. Because you run Jentic One yourself, your own rules decide which Spinbot operations and credentials the agent may use. Spinbot takes its article text and options in the request body rather than as a resource in the URL, so the honest boundary is by operation: you can allow your agent to extract an article with POST /api/article or generate spintax with POST /api/spintax while withholding POST /api/spinner and POST /api/pretty-spinner, and gate read-only calls like GET /api/acc for credit checks separately. The API key stays with your Jentic One instance and is injected only for the operations you permit.
For Agents
Programmatically return the user credit information., extracting the main article of the given url.. Covers 5 operations with apiKey authentication.
Use for: I need to return the user credit information., I want to extracting the main article of the given url., Search for human readable auto rewrite your article., Find all rewriting (spinning) your input article.
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Spinbot.net propose a new solution based on high technologies for faster article spinner and extractor that you will love to use it. The API exposes 5 endpoints secured with apiKey authentication.