Developer-Tools
Overview
Aqteron helps you create, publish, and update web apps with Claude. Connect your Aqteron account so Claude can read the current app-building requirements, list your existing apps, transfer and validate app ZIP packages, and publish a new app or update an existing one. Published apps can be opened and shared by link. Each user signs in to their own Aqteron account and approves access through OAuth. Uploading a package and publishing an app are separate steps. You can revoke the connection from your Aqteron account. An Aqteron account is required. Building and transferring ZIP packages requires a Claude environment with code execution and file access.
Tools
Appends a standard-base64 ZIP chunk to the connected account's pending transfer at the next zero-based index. Chunks are sequential and bounded by the transfer's chunk_bytes. Identical retries are idempotent. Returns transfer progress and next_chunk_index. Does not validate or publish the package.
begin_app_zip_upload
ClaudeCreates or resumes a ZIP transfer for the connected account using the exact byte size and SHA-256. Supports clients without file attachment transport. Returns transfer_id, chunk_bytes and next_chunk_index. Create mode has no target identifiers; update mode requires an owned target and expected_version_id. Does not validate or publish the package.
complete_app_zip_upload
ClaudeFinalizes a fully received ZIP transfer by checking its exact byte length and SHA-256 and running Aqteron package validation. Returns operation_id, validation status, errors and warnings. Repeated requests for the same transfer return the same operation. Does not publish the package.
deploy_app
ClaudePublishes a validated ZIP operation owned by the connected account. Creates a public application or replaces an owned application's active version, with a version-conflict check for updates. Inputs identify the validated operation and an idempotency key. Returns deployment state, app and version identifiers, errors and the public URL on success.
get_app_instructions
ClaudeReturns current account-specific Aqteron documentation for application creation and modification: SDK contracts, available platform capabilities, ZIP package format, validation requirements and the specialist workflow. The response includes complete generationContext.builder.modules with contentMarkdown and a versioned specialist catalog. An optional specialist_request returns task-specific prompts in the same response. Requires a connected account; no existing app, ZIP or generation-context locator is needed. Read-only.
get_deploy_status
ClaudeReturns the connected account's ZIP or deployment operation state, including stage, errors, warnings, app and version identifiers, checksum and the public URL when publication succeeds. Read-only.
get_specialist_instructions
ClaudeReturns Aqteron's versioned specialist prompts, selection reasons, stage deliverables and acceptance checks for an agreed application task. Covers planning, design, implementation and verification. Selection includes baseline architecture, design, accessibility, security and QA plus mobile, 3D, game, data and performance specialists as needed. Explicit features and additional specialist IDs support AI-selected expertise. Responses contain workflow prerequisites; fetching prompts does not execute tests or certify a build. Account-scoped, read-only.
list_apps
ClaudeReturns applications owned by the connected Aqteron account, including identifiers and current active versions for update target selection. Public tokens identify applications without granting access. Read-only.
open_aqteron_generation_context
ClaudeReturns the generation-safe Aqteron context associated with an existing exact /g/ locator, including platform documentation and available capabilities. Read-only; cannot create, renew, revoke or modify a context.
upload_app_zip
ClaudeImports a ZIP from a supported runtime file attachment into the connected account and validates the package without publishing it. Inputs include the attachment reference, exact byte size, optional SHA-256 and matching app name. Create mode has no target identifiers; update mode requires an owned target and expected_version_id, which is null for an unpublished app. Returns a package operation and validation results.






