canonical: https://jentic.com/apis/swaggerhub.asuite-developers/adminasuiteorg

# Asuite Developers admin.asuite.org

swaggerhub.asuite-developers/admin-swagger version 1.0.0. The API exposes 7 endpoints secured with apiKey authentication.

## For AI agents

Programmatically postwpv2users, getwpv2users. Covers 7 operations with apiKey authentication.

## Scope

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

## Capabilities

- PostWpV2Users
- GetWpV2Users
- DeleteWpV2UsersById
- PostWpV2Settings
- GetWpV2Settings

## Use cases

### Developer Tools Operations

Use the admin.asuite.org to perform developer tools operations programmatically. The API provides 7 endpoints covering core functionality including postwpv2users, getwpv2users, postwpv2usersbyid.

Example prompt: Call POST `/wp/v2/users` to postwpv2users

### Automated Wp Management

Automate wp operations by combining multiple admin.asuite.org endpoints. Agents can getwpv2users and then postwpv2usersbyid in a single workflow.

Example prompt: Call GET `/wp/v2/users` to getwpv2users, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call admin.asuite.org 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 'postwpv2users', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/wp/v2/users` | PostWpV2Users |
| GET | `/wp/v2/users` | GetWpV2Users |
| POST | `/wp/v2/users/{id}` | PostWpV2UsersById |
| GET | `/wp/v2/users/{id}` | GetWpV2UsersById |
| DELETE | `/wp/v2/users/{id}` | DeleteWpV2UsersById |
| POST | `/wp/v2/settings` | PostWpV2Settings |
| GET | `/wp/v2/settings` | GetWpV2Settings |

## Key resources

- **Wp** — Operations for wp

## Why Jentic

- **Setup:** This admin.asuite.org API uses an X-WP-Nonce API key header and a host that embeds your tenant short name, so hand-wiring it means learning the WordPress nonce scheme, filling in your instance host, and handling retries yourself. Through Jentic you install once, import admin.asuite.org from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** This API puts the user id in the URL path (`/wp/v2/users/{id}`), so a rule can pin your agent to reading a single user. You choose the operations it may call, so destructive ones like user deletion or settings writes are not included unless you add them.
- **Credential handling:** Your admin.asuite.org 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 'create a WordPress user' or 'read the site settings', and Jentic returns the matching admin.asuite.org 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 admin.asuite.org use?

The admin.asuite.org uses an API key passed in the `X-WP-Nonce` 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 postwpv2users with the admin.asuite.org?

Yes. Use the POST `/wp/v2/users` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the admin.asuite.org?

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 postwpv2users through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'postwpv2users'. Jentic returns the matching admin.asuite.org operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the admin.asuite.org have?

The admin.asuite.org exposes 7 endpoints covering wp operations.

### Can I limit what my agent is allowed to do with the admin.asuite.org API?

Yes. Jentic One is self-hosted by you, so your own rules decide which admin.asuite.org operations and credentials the agent may use. Because the user id sits in the URL path (`/wp/v2/users/{id}`), you can pin the agent to reading a single user with GET `/wp/v2/users/{id}` while withholding destructive calls like DELETE `/wp/v2/users/{id}` or the POST `/wp/v2/settings` write. The agent can only call the operations you explicitly grant, and the API key stays encrypted in your instance and is injected at execution time.