canonical: https://jentic.com/apis/swaggerhub.absie0873/terms-and-conditions

# Absie0873 Terms and Conditions

Tracks whether a user has accepted the latest terms and conditions. The API exposes 3 endpoints.

## For AI agents

Programmatically newterms, accepttandc. Covers 3 operations.

## Scope

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

## Capabilities

- newTerms
- acceptTandC
- showTandC
- Query and filter Terms and Conditions records by parameters
- Monitor Terms and Conditions operational status and events

## Use cases

### Developer Tools Operations

Use the Terms and Conditions to perform developer tools operations programmatically. The API provides 3 endpoints covering core functionality including newterms, accepttandc, showtandc.

Example prompt: Call POST /terms-and-conditions to newterms

### Automated terms-and-conditions Management

Automate terms-and-conditions operations by combining multiple Terms and Conditions endpoints. Agents can accepttandc and then showtandc in a single workflow.

Example prompt: Call POST `/terms-and-conditions/accept` to accepttandc, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Terms and Conditions 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 'newterms', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/terms-and-conditions` | newTerms |
| POST | `/terms-and-conditions/accept` | acceptTandC |
| GET | `/terms-and-conditions/show` | showTandC |

## Key resources

- **terms-and-conditions** — Operations related to terms-and-conditions

## Why Jentic

- **Setup:** Wiring the Terms and Conditions API by hand means pointing at its SwaggerHub virtual server and coordinating its create, accept, and show calls yourself, even though it takes no auth. Through Jentic you install once, import the Terms and Conditions API from the API Directory, and your agent calls it with no credential to manage.
- **Permission scoping:** These Terms and Conditions operations carry their targets in the request body, so scope your agent to the operations it needs, such as showing the current terms. You choose that set, so a write like accepting or creating terms is only included if you add it.
- **Credential handling:** This API takes no credential, so there is nothing to store, and your own Jentic One instance still injects any configured settings at execution time. No secret enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'show the current terms' or 'accept the terms and conditions', and Jentic returns the matching Terms and Conditions 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 Terms and Conditions use?

The Terms and Conditions 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.

### Can I newterms with the Terms and Conditions?

Yes. Use the POST /terms-and-conditions endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Terms and Conditions?

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

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

### How many endpoints does the Terms and Conditions have?

The Terms and Conditions exposes 3 endpoints covering terms-and-conditions operations.

### Can I limit what my agent is allowed to do with the Terms and Conditions API?

Yes. Because you run Jentic One yourself, you decide which of the Terms and Conditions operations your agent may call, and your own rules govern access at execution time. Each operation carries its target in the request body, so you can grant read-only access by allowing only the show current terms call (GET `/terms-and-conditions/show`) and withholding the rest. A write operation like accepting terms (POST `/terms-and-conditions/accept`) or creating new terms (POST /terms-and-conditions) is available to the agent only if you add it to that allowed set.