Aryeo API

Name: Aryeo API
Brand: Aryeo API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaImage Processingbearer7 EndpointsREST

For Agents

Read real estate listings, place media-shoot orders, and look up appointments in the Aryeo real estate media platform.

Install Jentic One Beta

Connect the Aryeo API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Aryeo API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Aryeo API.

Retrieve a paginated list of real estate listings with associated media

Place a new media-shoot order against a listing

Look up the status of a placed media order by order ID

Pull appointment details for scheduled property shoots

GET STARTED

Start building with Aryeo API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Aryeo API, keeping it validated and agent-ready. Aryeo is a real estate media management platform that connects photographers, agents, and brokerages to manage listings, media deliverables, and shoot orders. The API exposes 7 read and order-management endpoints covering listings, orders, and appointments, secured with bearer token authentication. It is designed for partners who need programmatic access to listing media and shoot scheduling rather than full storefront management.

Use Cases

Patterns agents use Aryeo API for, with concrete tasks.

★ Listing-to-Shoot Automation

When a new property is added to a brokerage's CRM, automatically create the corresponding media-shoot order in Aryeo. The /orders endpoints accept an order tied to an existing listing, removing the manual handoff between agents and the media coordination team. Suitable for brokerages running 50+ listings per week.

Create a new order in Aryeo for listing ID 'abc123' for a standard photo and 3D tour package and return the order ID

Appointment Confirmation Workflow

Pull upcoming media appointments from Aryeo and surface them in agent calendars or chat tools. The /appointments endpoints return scheduled shoots so an agent can confirm timing with the homeowner, send reminders, and update the brokerage's operations dashboard. Useful where photographers and listing agents coordinate across multiple platforms.

List Aryeo appointments scheduled in the next 48 hours and produce a homeowner-confirmation message for each

Listing Media Sync

Use the /listings endpoints to keep external systems - websites, CRMs, MLS feeds - synchronised with Aryeo's listing records and media references. Agents can poll listings for changes and trigger downstream publishing flows whenever new photography or 3D tours are delivered.

Fetch all Aryeo listings updated in the last 24 hours and publish their media URLs to a brokerage CMS

AI Agent for Real Estate Media Operations

An agent integrated through Jentic can monitor new listings, automatically place shoot orders, and confirm appointment changes - coordinating photographers, agents, and homeowners without bespoke integration code. Jentic isolates the Aryeo bearer token in the credential vault so the agent never holds raw secrets.

Through Jentic, watch for new brokerage listings and place corresponding Aryeo orders, then confirm each appointment with the listing agent

Key Endpoints

7 endpoints — jentic publishes the only available openapi specification for aryeo api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/listings

List listings

GET

/listings/{listing_id}

Get listing

POST

/orders

Create order

GET

/orders

List orders

GET

/orders/{order_id}

Get order

GET

/appointments

List appointments

GET

/appointments/{appointment_id}

Get appointment

GET

/listings

List listings

GET

/listings/{listing_id}

Get listing

POST

/orders

Create order

GET

/orders

List orders

GET

/orders/{order_id}

Get order

GET

/appointments

List appointments

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Aryeo bearer token 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.

Intent-based discovery

Agents search Jentic by intent such as 'place a real estate media order', and Jentic returns the POST /orders operation with its input schema so the agent calls the right endpoint without reading the Aryeo docs.

Time to first call

FAQs

Specific to using Aryeo API through Jentic.

Why is there no official OpenAPI spec for Aryeo API?

Aryeo does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Aryeo API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Aryeo API use?

The API uses HTTP bearer token authentication, passed in the Authorization header as 'Bearer {token}'. When called through Jentic, the token is stored in the Jentic credential vault and injected at execution time so it never enters the agent's context.

Can I create a media-shoot order through the Aryeo API?

Yes. POST /orders accepts a new media-shoot order tied to an existing listing. The same endpoint set supports listing all orders and retrieving a single order by ID for status checks.

What are the rate limits for the Aryeo API?

The OpenAPI specification does not publish explicit rate limits. Implement exponential backoff on HTTP 429 responses and cache /listings reads where freshness allows, since listing metadata changes infrequently between shoots.

How do I place an order through Jentic?

Search Jentic for 'create a real estate media order' and the POST /orders operation will be returned. Load the operation schema, supply the listing_id and order details, and execute. Jentic handles authentication and returns the created order ID to the agent.

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

Yes. Because you run Jentic One yourself, your own rules decide which Aryeo operations and credentials the agent may use. Aryeo puts the listing and order id in the URL path, such as /orders/{order_id} and /listings/{listing_id}, so you can pin the agent to reads of a single order or listing. You choose the operations it may call, which means placing new media-shoot orders through POST /orders is excluded unless you explicitly grant it.

Aryeo API

Connect the Aryeo API to your agent

Capabilities

Start building with Aryeo API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs