---
title: "aecon.ai developer resources"
description: "Connect your agent to the Agentic Economy API marketplace. Start with public discovery, then follow the current authentication and Tool contracts."
url: https://aecon.ai/developers
lang: en-AU
---

# aecon.ai developer resources

Connect your agent to the Agentic Economy API marketplace. Start with public discovery, then follow the current authentication and Tool contracts.

Source: https://aecon.ai/developers

## Public API quickstart

The marketplace API lives at https://app.aecon.ai. Public list, search, describe and compare operations require no account. The OpenAPI specification declares their exact HTTP methods, input schemas and responses.

Begin with a catalogue status read. It reports freshness; a stale or partial catalogue cannot establish that a Tool is absent. Search by the outcome you need, then describe the exact Tool reference returned by search.

A Tool is the catalogue’s description of an outside service. Search returns candidates; describe the returned reference to inspect the information it needs and the work it returns. Read-only discovery does not grant account or purchase access.

```sh
# Check catalogue freshness
curl --fail-with-body 'https://app.aecon.ai/api/v1/catalogue-status'

# Search without creating a quote or purchase
curl --fail-with-body 'https://app.aecon.ai/api/v1/market-tools/search' \
  -H 'Content-Type: application/json' \
  --data '{"query":"find web research sources"}'
```

- [OpenAPI specification](https://app.aecon.ai/openapi.json)
- [API and CLI reference](https://app.aecon.ai/llms.txt)
- [Agent instructions and search example](https://aecon.ai/agents.md)

## Connect an agent and manage API keys

Use the marketplace setup flow for your existing agent app, or manage an Agent access key in your signed-in account. Direct protected HTTP requests send the key as Authorization: Bearer. Keep keys out of browser code, public prompts and support messages.

For MCP, configure https://app.aecon.ai/mcp using Streamable HTTP. Initialise the connection and request tools/list; use only the names and schemas returned. OAuth protected-resource metadata identifies the authorization server. A connection or key does not grant spending authority; protected Calls require market_tools:call scope and a current quote.

Connect at https://app.aecon.ai/mcp. Add ?readonly=1 (https://app.aecon.ai/mcp?readonly=1) to discover and read account data without buying or writing.

- [Agent setup and authentication](https://app.aecon.ai/for-agents)
- [Manage Agent access keys (sign-in required)](https://app.aecon.ai/agent-access)
- [OAuth resource metadata](https://app.aecon.ai/.well-known/oauth-protected-resource)
- [Marketplace skill and recovery contracts](https://app.aecon.ai/SKILL.md)

## Try public discovery and check availability

Public discovery and the free website readiness scan are available without an account or payment. The quickstart reads catalogue status and searches for services; it creates no Tool quote, purchase or payment. The readiness scan uses the website's browser workflow and request limits.

The OpenAPI document includes /api/v1/sandbox-reference, but that counterparty is development-only and the public deployment rejects it. A public payment sandbox, test credentials and production funding or purchases are not advertised as available. Check launch status before protected work. Account sign-in is required to manage keys; this website does not issue them.

- [Scan a website for free](https://aecon.ai/agent-native-index)
- [Launch status](https://aecon.ai/launch)
- [Pricing and availability](https://aecon.ai/pricing.md)

## API versions, rate limits and deprecation

Use the /api/v1 paths and schemas declared by the marketplace's current OpenAPI document. Keep x-ae-request-id with a request result. On a 429, respect Retry-After when supplied and retry only when the response allows it. After an unknown Call outcome, read its status before retrying with the original idempotency key.

Quota response headers, a guaranteed deprecation notice period and a sunset schedule are not yet published as marketplace guarantees. Confirm those operational terms before depending on the API in production. This website cannot set marketplace quotas or retire its endpoints.

Deprecation uses a structured date under RFC 9745; Sunset uses an HTTP date under RFC 8594. RateLimit and RateLimit-Policy are defined by the current IETF HTTPAPI draft. These references explain the formats; their presence here does not assert that the marketplace emits those headers.

- [Deprecation header specification](https://www.rfc-editor.org/rfc/rfc9745.html)
- [Sunset header specification](https://www.rfc-editor.org/rfc/rfc8594.html)
- [IETF rate-limit header draft](https://datatracker.ietf.org/doc/html/draft-ietf-httpapi-ratelimit-headers-11)