canonical: https://jentic.com/apis/swaggerhub.wwwadzapi/api-materialservice

# Wwwadzapi API material_service

211 - material_service. Описание API. The API exposes 4 endpoints.

## For AI agents

Programmatically registermaterialsselect, findmaterialbyuuid. Covers 4 operations.

## Scope

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

## Capabilities

- registerMaterialsSelect
- findMaterialByUuid
- getPartners
- filter
- Monitor API material_service operational status and events

## Use cases

### Developer Tools Operations

Use the API material_service to perform developer tools operations programmatically. The API provides 4 endpoints covering core functionality including registermaterialsselect, findmaterialbyuuid, getpartners.

Example prompt: Call POST `/materials/register` to registermaterialsselect

### Automated filter-controller Management

Automate filter-controller operations by combining multiple API material_service endpoints. Agents can findmaterialbyuuid and then getpartners in a single workflow.

Example prompt: Call GET `/materials/{uuid}` to findmaterialbyuuid, then verify the result

### AI Agent Integration via Jentic

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/materials/register` | registerMaterialsSelect |
| GET | `/materials/{uuid}` | findMaterialByUuid |
| GET | `/materials/partners` | getPartners |
| POST | `/materials/{partner_id}` | filter |

## Key resources

- **filter-controller** — Запросы и фильтрация списка материалов с указанием идентификатора партнёра
- **material-uuid-controller** — Запросы состава набранных материалов по UUID
- **partner-controller** — Запросы информации о партнерах провайдерах материалов

## Why Jentic

- **Setup:** Wiring the material_service API by hand means coding its register and lookup calls and shaping each material payload against its host yourself. Through Jentic you install once, import the material_service API from the API Directory, and your agent calls it.
- **Permission scoping:** The material_service API puts the material and partner id in the URL path (`/materials/{uuid}`, `/materials/{partner_id}`), so a rule can pin your agent to one material or partner: it can read that record and nothing else. You choose the operations it may call, so writes like registering a material are not included unless you add them.
- **Credential handling:** Any credential you configure for the material_service API 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 'register a material' or 'get a material by id', and Jentic returns the matching material_service 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 API material_service use?

The API material_service 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 registermaterialsselect with the API material_service?

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

### What are the rate limits for the API material_service?

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

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

### How many endpoints does the API material_service have?

The API material_service exposes 4 endpoints covering filter-controller, material-uuid-controller, partner-controller operations.

### Can I limit what my agent is allowed to do with the material_service API?

Yes. Because you self-host Jentic One, your own rules decide which material_service operations and credentials the agent may use. Since the material and partner IDs sit in the URL path (`/materials/{uuid}`, `/materials/{partner_id}`), a rule can pin the agent to a single material or partner and let it read that record and nothing else. You choose which operations it may call, so a write like POST `/materials/register` stays off limits unless you add it.