Tenant-scoped access
Each approved bearer credential resolves to one current dealership. Account and photo lookups remain inside that dealership boundary.
Read-only MCP private early access
Automotive photo workflow API & MCP integration
Connect approved AI assistants and dealership tools to existing CarPixAI account, background, photo-status, and completed-result data—without giving external automation permission to upload, process, spend credits, or publish.
Approved dealership accounts only · Bearer-protected · Streamable HTTP · Read-only
Available today
Useful access with narrow authority
The first integration slice is deliberately read-only. It helps approved systems understand existing CarPixAI work without creating new paid or externally visible actions.
Account and background context
Read the dealership account, current processing-credit balance, assigned background templates, and enabled automotive scene styles.
Existing photo-job status
Inspect an owned photo job or request the narrower safe status view without exposing internal prompts, settings, or storage URLs.
Authenticated completed results
Retrieve an existing completed result through CarPixAI's protected presentation export path using the same approved credential.
Current boundary
Read-only means read-only
CarPixAI models and connected clients may coordinate a permitted read. They do not own authority over dealership identity, inventory, media, credits, processing, exports, or publishing.
Not available in this release
- Processing creation is not available through MCP or a public developer API.
- External tools cannot upload inventory, spend credits, or approve paid work.
- Direct DMS, inventory-feed, marketplace, website, and publishing connectors are not yet available.
- Self-service API keys, OAuth, webhooks, a customer CLI, and public processing rate limits are not yet offered.
Practical uses
Connect safely before automating writes
Give an AI assistant dealership context
Let an approved MCP client answer questions about the connected account, assigned backgrounds, and one known photo job without granting write authority.
Check existing work from another tool
Use photo-status reads to surface whether an owned CarPixAI image is pending, processing, completed, or failed inside a dealership operations workflow.
Deliver an approved existing result
Request completed output through the authenticated CarPixAI export boundary rather than exposing a raw provider or storage URL.
One platform, progressively released surfaces
The public Photo Grader already uses a bounded CarPixAI agent capability. MCP is the first external dealership integration. REST, CLI, paid processing, and connectors will reuse shared typed capability and domain-service authority as each release gate is proven.
Public Photo Agent: available
Read-only MCP: private early access
Shared status REST: preview
Paid processing writes: not released
DMS/feed publishing connectors: not released
Integration FAQ
What approved teams can expect
Is the CarPixAI integration a public image-processing API?
Not yet. The current external integration is read-only MCP private early access for approved dealership accounts. It can read existing account, background, photo-status, and completed-result data; it cannot create processing work.
Can an MCP client process photos or spend dealership credits?
No. Processing, uploads, approvals, and credit spending remain inside CarPixAI's authoritative dealer workflow. External writes will stay unavailable until durable approval, atomic reservation, rate-limit, retry, and reconciliation requirements are verified together.
Does CarPixAI integrate directly with a DMS or listing feed today?
No direct DMS, inventory-feed, marketplace, website, or publishing connector is currently offered. CarPixAI is accepting qualified workflow requirements from dealerships and integration partners while those connector boundaries are developed.
How is dealership data protected?
Approved bearer credentials resolve to one dealership at request time. Tool queries enforce dealership ownership, errors are sanitized, and completed media is delivered through an authenticated CarPixAI export route rather than a raw storage URL.
How do I request private early access?
Email CarPixAI with the dealership, client or workflow you want to connect. Access is manually reviewed and provisioned for approved dealership accounts during this first read-only phase.
Describe the workflow you want to connect
Tell us which dealership account, MCP client, internal tool, or future DMS workflow you are evaluating. Early access is manually reviewed and provisioned.
Request private early access