Repository navigation
feat(make): add five independent service apps and chat companion - #800
Open
acedatacloud-dev wants to merge 11 commits into
Open
acedatacloud-dev wants to merge 11 commits into
acedatacloud-dev wants to merge 11 commits into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
User-visible scope
Prepare five independently deployable service apps for Make: Suno, Seedance, HappyHorse, GPT Image, and Nano Banana, each identified as provided by Ace Data Cloud. Users should find a service-specific entry and use native generation/task fields rather than hand-writing HTTP calls. The original chat app remains a companion. These are source projects, not publicly installed/listed apps.
Service-specific implementations
Each service app has its own Make manifest, API-token Connection, generation Action, same-ID task lookup, universal module, interfaces, EN/ZH illustrated onboarding, and publication packet. No separate empty repos or duplicate source PRs are created.
contentarray, 2.x text-to-video models, 480p/720p common supported choices, explicit duration/ratio/audio. Retrieve object status and nested or documented flat video URL.action=generate, t2v models only, uppercase 720P/1080P, 3/5/10/15 seconds. Retrieve its video array and succeeded state./openai/images/generations, explicit GPT Image 2/2.5 model/size/quality, one URL-format image (n=1),/openai/taskslookup anddata[0].urloutput.image_url.All new submissions use
async=true, preserve the task ID, avoid fake callback URLs/model fallbacks and do not configure automatic paid application-error replay. Pending/failed/partial/unrecognized task results do not expose final media. Query outputs are allowlisted and internal envelope fields are sanitized in request logs. These first modules do not claim full service API parity: edits/reference uploads/advanced actions remain outside the documented scope.Validation
f288eb461f15d057e9f5cedd634ce1e5c4959552provides the four distinct request/task contracts; schema fixtures retain source URLs. Source guide constraints supplement the broad enums (for example Seedance Fast/Mini resolution and Nano Banana Lite restrictions).python3 -m unittest discover -s scripts/tests -v: 32 passed. Includes service payloads, different result layouts, same IDs, one-based array paths, preview/partial/failed/empty task handling, interface parity, shared credentials and URL regressions. Limited expression simulation is not Make's real IML engine.git diff --checkpassed.474d258passed all nine checks: https://github.com/AceDataCloud/SDK/actions/runs/39101196966 . The PR remains OPEN and mergeable; the six manifests are validated in the Make schema job.Native-provider and publication gates
Make's public AI Agent API exposes fixed provider enums and GET inspection routes, with no documented public create-brand-provider route. A manual compatible connection does not make Ace a named/default provider. Provider facts and precise account inspection steps are prepared; no unsupported native-provider manifest is fabricated.
Official Custom App technical review and Community distribution have distinct service/brand/partner requirements. Community permits multiple partner apps for a service but signed-partner/default/roadmap gates and the historical FAQ need current verification. Proposed labels such as
Seedance by Ace Data Cloudidentify the integration provider, do not claim third-party affiliation, and remain subject to Make naming/trademark approval. Public Publish is irreversible and owner/legal confirmations remain required.All origins are empty: actual zone/app IDs/versions/organization/team and development credentials are unpaired. Real Make installation, IML execution, per-module fresh scenarios, redacted logs, separate approved generation-to-terminal media/unique billing, official listings and external installs remain pending. Source/CI and the Geocodify reference screenshot are not release evidence. No conversion/revenue claim is made.
No merge, production deployment, new cloud app/account, paid generation, legal acceptance, permission expansion or unsolicited third-party outreach occurred. Git/source changes are reversible. Adversarial review was not requested.