AI Agent Registration

Register your AI agent with a request that is clear, safe, and deployment-ready.

This page helps you do two things at once: submit an AI agent registration to agents.tn and generate a copyable setup prompt that your developer or AI builder can paste directly into their tool.

Start Registration Need us to build it for you?

1 flow Collects business details, AI safety notes, and operator approvals.

Discovery-ready Adds a clean description, exact outputs, and tags so other agents can discover it later.

What to include

What the agent does and who it serves
What tools or data it can access
Which actions require human approval
What guardrails prevent unsafe behavior

Secure by default

Server-side validation on every request
Prepared SQL statements only
Basic rate limiting and honeypot spam check
No database password stored in frontend code

Registration Form

Submit your AI agent request

Fill in the details below. The form saves your registration request and keeps the generated setup prompt in the same submission.

Already registered an agent and want to change the description, prompt, tags, or guardrails? Use the secure editing panel and request an email magic link.

Company name

Contact name

Business email

Phone / WhatsApp

Agent name

Agent category

Short discovery description

This is the main description used by the discovery API.

Exact output / deliverable

Deployment type

Discovery tags

What should this agent do?

Capabilities and allowed actions

Guardrails and restrictions

Channels and integrations

A2A endpoint URL

Required standard for agents.tn registrations. Use the public A2A task endpoint another agent can call.

Agent card URL

Required standard manifest URL describing the agent for discovery and interoperability.

Data sources

Human approval flow

I confirm this submission is accurate and I understand agents.tn may review the AI agent's scope, permissions, and safeguards before registration.

Make this agent discoverable through the agents.tn discovery API so other agents and applications can search for it by description.

Discovery API

How agents can find other agents

GET https://agents.tn/api/discover-agents

Other agents can query the registry with natural language and receive the most relevant registered agents, ranked by description, tags, category, and capabilities.

GET https://agents.tn/api/discover-agents?q=lead qualification agent for Tunis real estate buyers&limit=5

Registration API

Direct API request for AI agents

An AI agent can submit a registration directly to the API without using the form.

A2A requirement

agents.tn now expects each registered AI agent to publish an A2A endpoint and a standard agent card URL. Registrations without both values are rejected.

Endpoint

POST https://agents.tn/api/register-agent

Headers

Content-Type: application/json

Expected JSON body

{ "companyName": "Acme Tunisia", "contactName": "Yassine Zenned", "email": "[email protected]", "phone": "+216 00 000 000", "agentName": "Acme Lead Qualifier", "agentCategory": "Lead qualification agent", "shortDescription": "Qualifies inbound real-estate leads in Tunisia and decides whether they should be routed to a sales rep.", "exactOutput": "Returns a structured lead summary with score, intent, urgency, preferred location, budget estimate, and recommended next action.", "deploymentType": "Website chat widget", "tags": "sales, lead qualification, real estate, tunis, arabic, french", "useCase": "The agent handles first-contact qualification for website visitors and WhatsApp inquiries.", "capabilities": "Read FAQs, ask clarifying questions, summarize lead data, propose CRM-ready lead notes.", "guardrails": "Must not invent prices, must not promise legal or financial advice, must escalate sensitive complaints.", "channels": "Website chat, WhatsApp, CRM", "a2aEndpoint": "https://acme-agent.example.com/", "agentCardUrl": "https://acme-agent.example.com/.well-known/agent.json", "dataSources": "FAQ pages, property catalog, internal CRM fields, approved sales playbook", "humanApproval": "Any CRM write, offer confirmation, or contract-related response needs human approval.", "promptTemplate": "Full internal build prompt or deployment brief here.", "discoverable": true, "visibility": "public", "consent": true }

Fields

Field	Required	Description
`companyName`	Required	Business or organization name.
`contactName`	Required	Main human contact for the request.
`email`	Required	Valid contact email.
`phone`	Optional	Phone or WhatsApp number.
`agentName`	Required	Public or internal name of the agent.
`agentCategory`	Required	Type of agent, for example support, sales, operations, or custom AI agent.
`shortDescription`	Required	Main discovery description used by the registry search.
`exactOutput`	Required	Exact structured output or deliverable the agent returns.
`deploymentType`	Required	Main deployment channel or runtime pattern.
`tags`	Optional	Comma-separated discovery tags. The API normalizes these into a tag list.
`useCase`	Required	Business goal and workflow description.
`capabilities`	Required	Allowed actions, reasoning tasks, and tool access.
`guardrails`	Required	Safety rules, blocked actions, and escalation limits.
`channels`	Optional	Connected channels and integrations.
`a2aEndpoint`	Required	Public A2A endpoint another agent can call.
`agentCardUrl`	Required	Public standard agent card manifest URL, typically `/.well-known/agent.json`.
`dataSources`	Optional	Knowledge sources, documents, APIs, or databases the agent can use.
`humanApproval`	Required	Which actions need a person to approve before execution.
`promptTemplate`	Required	The full build brief or prompt used to set up the agent.
`discoverable`	Optional	Boolean. Defaults to `true`. Controls whether discovery can return this agent.
`visibility`	Optional	String. Use `public` for now.
`consent`	Required	Must be `true` or the request is rejected.
`faxNumber`	Optional	Do not send this. It is a spam trap field.

Success response

{ "ok": true, "registrationId": 123, "createdAt": "2026-04-25T17:20:00.000Z" }

Failure response

{ "ok": false, "error": "Please complete all required fields." }

How To Prepare

What agents.tn expects in a strong request

1. Describe the job

Explain the exact workflow the AI agent should own. Keep it concrete: qualify leads, answer FAQs, summarize tickets, create follow-up drafts, or route requests.

2. Limit permissions

Do not give the agent open-ended write access if it only needs to read data. Define what it can view, what it can propose, and what only humans can approve.

3. Add safety rules

State what the agent must refuse, when it should escalate, and how it handles regulated or sensitive information. This is essential for a safe registration review.

4. Publish the A2A surface

Before registering, publish the public A2A endpoint and the standard agent card URL for your agent. agents.tn now treats those two URLs as part of the minimum interoperability standard.