canonical: https://jentic.com/apis/spinbot.net/spinbot

# Spinbot Article Rewriter and Article Extractor API

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.

## For AI agents

Programmatically return the user credit information., extracting the main article of the given url.. Covers 5 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- 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

## Use cases

### 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..

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'return the user credit information.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/acc` | Return the user credit information. |
| POST | `/api/article` | Extracting the main article of the given URL. |
| POST | `/api/pretty-spinner` | Human readable auto rewrite your article. |
| POST | `/api/spinner` | Rewriting (spinning) your input article. |
| POST | `/api/spintax` | Generate Spintax format for the input article |

## Key resources

- **article rewriter** — Article rewriter (spinner): rewrite your origin article by replacing every terms/words to their syno
- **article extractor** — Article extractor: a lot of techniques and mordern algorithms like machine learning are used to dete

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### 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.