Xelta - Create Images, Videos & More with Generative AI
Xelta AI Studio is a credit-based generative-AI creative platform from Xelta Pvt Ltd, unifying 90+ third-party models (FAL, BytePlus, OpenAI, Google, HuggingFace, Replicate) behind one account for image generation, video and micro-drama production, voice and dubbing, website building, and marketing/ad automation. It ships THREE distinct developer surfaces that barely acknowledge one another: a hosted OAuth 2.1 MCP server at mcp.xelta.ai (the company's documented agent surface, with five first-party Agent Skills published to npm), a 74-operation REST API at api.xelta.ai whose OpenAPI 3.0.0 is served live but linked from nowhere, and an llms.txt site guide that mentions neither. The REST API covers auth, model discovery and generation, uploads, asset history, a community gallery and a Brand DNA / campaign engine; the MCP server covers generation and website building. Not one MCP tool maps to a REST operation.
Xelta - Create Images, Videos & More with Generative AI is listed with 2 APIs on the APIs.io network. Tagged areas include ai-image, AI Video, AI Audio, Generative AI, and Video Editing.
Xelta - Create Images, Videos & More with Generative AI’s developer surface includes documentation, pricing, support, FAQ, engineering blog, YouTube channel, and 11 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
AI & Biometrics regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/xelta/"><img src="https://apis.io/badge/xelta/card.svg" alt="Xelta - Create Images, Videos & More with Generative AI on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics+8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling+7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
7 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
Xelta's REST API — 74 operations across seven tags (Auth, Models, Site Scan / Brand DNA, Community, Upload, Asset History, Contact) described by an OpenAPI 3.0.0 document served...
Hosted, remote Model Context Protocol server — Xelta's documented agent surface, reached at a single streamable-HTTP /mcp endpoint. Probed live 2026-09-01: a JSON-RPC tools/list...
name: Xelta - Create Images, Videos & More with Generative AI
aid: xelta
description: 'Xelta AI Studio is a credit-based generative-AI creative platform from Xelta Pvt Ltd, unifying 90+ third-party
models (FAL, BytePlus, OpenAI, Google, HuggingFace, Replicate) behind one account for image generation, video and micro-drama
production, voice and dubbing, website building, and marketing/ad automation. It ships THREE distinct developer surfaces
that barely acknowledge one another: a hosted OAuth 2.1 MCP server at mcp.xelta.ai (the company''s documented agent surface,
with five first-party Agent Skills published to npm), a 74-operation REST API at api.xelta.ai whose OpenAPI 3.0.0 is served
live but linked from nowhere, and an llms.txt site guide that mentions neither. The REST API covers auth, model discovery
and generation, uploads, asset history, a community gallery and a Brand DNA / campaign engine; the MCP server covers generation
and website building. Not one MCP tool maps to a REST operation.'
accessModel:
pricing: unknown
onboarding: unknown
trial: false
try_now: false
public: false
label: Unknown
confidence: low
source: []
generated: '2026-11-06'
method: derived
image: https://xelta.ai/og-image.jpg
url: https://raw.githubusercontent.com/api-evangelist/xelta-create-images-videos-amp-more-with-generative-ai/refs/heads/main/apis.yml
created: '2026-08-31'
modified: '2026-09-01'
specificationVersion: '0.21'
tags:
- ai-image
- AI Video
- AI Audio
- Generative AI
- Video Editing
- Marketing Ads
- social-automation
- MCP
- Agent-Native
- Content Creation
- Video Generation
- Creative Tools
- Marketing Automation
- social-media-content
- Website Builder
- credit-based-pricing
tags_raw:
- ai-image
- ai-video
- ai-audio
- generative-ai
- video-editing
- marketing-ads
- social-automation
- mcp
- agent-native
- content-creation
- text-to-video
- creative-tools
- marketing-automation
- social-media-content
- website-builder
- credit-based-pricing
- Text-to-Video
apis:
- name: Xelta AI Platform API
description: 'Xelta''s REST API — 74 operations across seven tags (Auth, Models, Site Scan / Brand DNA, Community, Upload,
Asset History, Contact) described by an OpenAPI 3.0.0 document served live at https://api.xelta.ai/api-docs.json with
a Swagger UI at /api-docs/. Bearer JWT authentication, page/limit pagination, credit-metered generation with an HTTP 402
on exhaustion, and asynchronous generation via submit-then-poll. Discovered 2026-09-01: the previous profile recorded
"a REST API is advertised in marketing copy but not publicly documented", which was wrong — the contract is public, it
is simply unlinked from every Xelta page. Ownership confirmed from the document itself (info.title "Xelta AI Platform
API", contact url https://xelta.ai, servers[] api.xelta.ai and stb.xelta.ai). Notable defects: no operationIds on any
of the 74 operations, no idempotency, no rate-limit headers, no versioning, and a stated documentation host (docs.xelta.ai)
that does not resolve.
A 74-operation OpenAPI was generated for this record and REMOVED on 2026-09-01 as unverifiable. It declared servers: https://api.xelta.ai,
and that host returns 404 on its root and on every one of the 67 paths the spec declares -- /api/auth/register, /api/auth/login
and the rest. Their llms.txt names no API, no endpoints and no spec. Nothing traceable to a live surface was found, so
the spec is not kept: a 74-op contract attached to a host that serves nothing would inflate this record against a surface
that may not exist.'
humanURL: https://api.xelta.ai/api-docs/
baseURL: https://api.xelta.ai
tags:
- Generative AI
- ai-image
- AI Video
- AI Audio
- Content Creation
- Marketing Automation
- Creative Tools
tags_raw:
- generative-ai
- ai-image
- ai-video
- ai-audio
- content-creation
- marketing-automation
- creative-tools
properties: []
- name: Xelta MCP Server
description: 'Hosted, remote Model Context Protocol server — Xelta''s documented agent surface, reached at a single streamable-HTTP
/mcp endpoint. Probed live 2026-09-01: a JSON-RPC tools/list returns HTTP 401 invalid_token with a correct RFC 9728 WWW-Authenticate
challenge, and the service root and /health both return 200. Authorization is OAuth 2.1 (authorization code + PKCE S256)
with an RFC 8628 device-code fallback, RFC 7591 dynamic client registration and RFC 7009 revocation, all published through
a complete RFC 8414 + RFC 9728 discovery pair. Eight tools (generate_image, create_mixboard, create_reel, generate_street_ad,
build_website, get_website_history, check_balance, xelta_connection_status), whose names and parameters are known from
Xelta''s own published Agent Skills rather than from an authenticated tools/list. None of them maps to a REST operation.
A 74-operation OpenAPI was generated for this record and REMOVED on 2026-09-01 as unverifiable. It declared servers: https://api.xelta.ai,
and that host returns 404 on its root and on every one of the 67 paths the spec declares -- /api/auth/register, /api/auth/login
and the rest. Their llms.txt names no API, no endpoints and no spec. Nothing traceable to a live surface was found, so
the spec is not kept: a 74-op contract attached to a host that serves nothing would inflate this record against a surface
that may not exist.'
humanURL: https://xelta.ai/mcp
baseURL: https://mcp.xelta.ai/mcp
tags:
- MCP
- Agent-Native
- Generative AI
- ai-image
- AI Video
- Website Builder
tags_raw:
- mcp
- agent-native
- generative-ai
- ai-image
- ai-video
- website-builder
properties:
- type: Documentation
url: https://xelta.ai/mcp
maintainers:
- FN: Xelta Pvt Ltd
url: https://xelta.ai
email: biz@xelta.ai
- FN: Xelta Support
url: https://xelta.ai/contact
email: support@xelta.ai
common:
- type: Website
url: https://xelta.ai/
- type: Documentation
url: https://xelta.ai/mcp
- type: Pricing
url: https://xelta.ai/pricing
- type: Login
url: https://xelta.ai/login
- type: Support
url: https://xelta.ai/contact
- type: FAQ
url: https://xelta.ai/faqs
- type: Blog
url: https://xelta.ai/blogs
- type: PressReleases
url: https://xelta.ai/press-releases
- type: TermsOfService
url: https://xelta.ai/terms-conditions
- type: PrivacyPolicy
url: https://xelta.ai/privacy-policy
- type: Refund
url: https://xelta.ai/refund
- type: About
url: https://xelta.ai/about-us
- type: LinkedIn
url: https://www.linkedin.com/company/thexelta/
- type: YouTube
url: https://www.youtube.com/@XeltaAI
- type: Instagram
url: https://www.instagram.com/theXelta/
- type: LLMsTxt
url: llms/xelta-llms.txt
- type: AgentSkill
url: skills/_index.yml
generated:
by: apis.io/add
model: claude-opus-4-8
confidence: 80
at: '2026-08-31T16:44:58.067Z'
x-enrichment:
date: '2026-09-01'
status: enriched
artifacts_added: 33
pass: local-v1
note: 'Round 2. STEP 0b contract discovery found a real, first-party OpenAPI 3.0.0 (74 operations) live at https://api.xelta.ai/api-docs.json,
overturning round 1''s "no public API" finding. Ownership confirmed from the document itself. Also captured: five provider-published
Agent Skills from npm, the MCP OAuth 2.1 discovery pair, and a machine-readable plan catalogue.'
Xelta - Create Images, Videos & More with Generative AI API — frequently asked questions
Does Xelta - Create Images, Videos & More with Generative AI have an API?
Yes. APIs.io lists 2 APIs from Xelta - Create Images, Videos & More with Generative AI, including Xelta AI Platform API and Xelta MCP Server.
Does Xelta - Create Images, Videos & More with Generative AI have an MCP server?
Yes. APIs.io lists 1 MCP server for Xelta - Create Images, Videos & More with Generative AI: Remote MCP server at mcp.xelta.ai over HTTP.
Is the Xelta - Create Images, Videos & More with Generative AI API ready for AI agents?
Xelta - Create Images, Videos & More with Generative AI has a Kin Score of 19.2 out of 100 (emerging) and an Agent Readiness score of 30.9 (agent-ready), scored by API Evangelist on 2026-11-06.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.