canonical: https://jentic.com/apis/swaggerhub.direct-wines/address-party-domain-schemas

# Direct Wines Address Party Domain Schemas

Shared domain schemas for address and addressable party information. **Address** represents a physical location using ISO 19160-compliant fields: **AddressableParty** represents a named contact - with a nested Address: **CompanyContext** provides optional business context for commercial deliveries: In short: an Address is *where*; an AddressableParty is *who* lives or works there; a CompanyContext. The API exposes 0 endpoints.

## For AI agents

Programmatically access Address Party Domain Schemas resources.

## Scope

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

## Capabilities

- Access Address Party Domain Schemas resources via REST API
- Manage crm data programmatically
- Integrate Address Party Domain Schemas into automated workflows
- Query and filter Address Party Domain Schemas records by parameters
- Monitor Address Party Domain Schemas operational status and events

## Use cases

### CRM Operations

The API provides 0 endpoints for crm operations.

Example prompt: Execute a primary operation against the Address Party Domain Schemas

### Data Retrieval and Monitoring

Query Address Party Domain Schemas resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Address Party Domain Schemas endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Address Party Domain Schemas 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 'address party domain schemas', load the operation schema, and execute with Jentic-managed credentials

## Why Jentic

- **Setup:** Address Party Domain Schemas defines shared address and party data structures, so wiring it by hand means reading its OpenAPI definition and mapping those schemas into your own code yourself. Through Jentic you install once, import Address Party Domain Schemas from the API Directory, store any credential it needs once, and your agent works from the shared definitions.
- **Permission scoping:** Address Party Domain Schemas publishes data shapes rather than callable resource paths, so limit the agent to the operations it needs. You choose what it may call, so nothing beyond the definitions you allow is available to it.
- **Credential handling:** Any credential this API requires 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 'resolve the address and party schema', and Jentic returns the matching Address Party Domain Schemas definition with its input schema so the agent uses the right shape without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Address Party Domain Schemas use?

The Address Party Domain Schemas 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.

### What are the rate limits for the Address Party Domain Schemas?

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 use address party domain schemas through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'use address party domain schemas'. Jentic returns the matching Address Party Domain Schemas operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Address Party Domain Schemas have?

The Address Party Domain Schemas exposes 0 endpoints for crm operations.

### Does the Address Party Domain Schemas support pagination?

Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.

### Can I limit what my agent is allowed to do with the Address Party Domain Schemas?

Yes. Because Jentic One runs self-hosted in your own environment, your rules decide which Address Party Domain Schemas definitions the agent may load and use. Since this API publishes shared address and party data shapes rather than callable resource paths, you allow only the schema operations the agent actually needs, and nothing beyond those definitions is available to it. Any credential the API requires is injected at execution time under the same controls, so the agent never gains access you did not grant.