Adept review

Adept is an ML research and product lab, not a documented general-purpose API, SDK, CLI, or self-hosted server. Its stated goal is to help people and computers work together creatively. For developers, the clearest named integration surface is Adept Workflow Language (AWL), a custom language for composing multimodal web interactions on Adept’s models.

That places AWL at the agent-workflow layer: it is intended to compose interactions, while Adept’s models provide the underlying capabilities. Adept describes Fuyu-Heavy as a multimodal model designed specifically for digital agents. The company has also announced open-source Fuyu-8B and Persimmon-8B releases, but those releases are distinct from a documented commercial workflow service. Adept opened access to Adept Experiments in 2023; confirm with the company whether that offering or another product is currently available, and what it takes to connect it to your application.

Adept’s named developer surface is AWL, which the company calls an expressive, custom language for composing multimodal web interactions on its models. The vendor’s homepage material also names Fuyu-Heavy, Fuyu-8B, and Persimmon-8B. It does not give a developer-facing API contract in that material, so we can’t point to a documented REST API, authentication method, SDK, supported programming language, CLI, webhook, or plugin.

That makes the first integration step a sales or product-access question, not a package install. Ask Adept for the current AWL documentation, supported runtime, model access path, authentication, versioning, and examples. Confirm whether an API, SDKs, or other integration surfaces are available, and check that those support your language and deployment environment. The published AWL description establishes the workflow concept, but not how a team wires it into an existing codebase or handles errors and retries.

Adept’s pricing check, dated November 10, 2026 and marked low confidence, identifies enterprise access as custom-quote only. It lists no starting price, annual or monthly rate, free plan, free trial, seat limit, or usage limit. Adept’s public pricing position is therefore difficult to model before contacting sales; ask for a written quote and billing terms before estimating a production budget.

The vendor’s site gives no published billable unit in the pricing information reviewed, so developers cannot calculate how costs grow with requests, seats, model usage, or compute. Ask how overages are handled, whether there are minimum commitments, and whether access to AWL and models is priced separately. Fuyu-8B and Persimmon-8B have been announced as open-source releases, but those releases do not establish free hosted access to Adept’s agent workflows. Treat enterprise access and open model use as separate purchasing and deployment decisions.

Adept announced open-source releases of Fuyu-8B and Persimmon-8B. Its Persimmon-8B announcement calls the model fully permissively licensed, while the Fuyu-8B announcement does not name a license in the homepage text. Check each model’s repository and license before incorporating weights or code into a product; do not assume the licenses are identical.

Those model releases do not establish that AWL or Adept’s commercial agent workflows can be self-hosted. The vendor’s stated AWL use is on top of Adept’s models, so teams should clarify whether the workflow language or model service requires Adept-controlled infrastructure. Ask about data export, retention, and migration paths before sending customer data or making AWL central to an application. Without those terms, the open model releases may offer an alternative for model experimentation, but they do not by themselves remove potential service lock-in.

Adept announced SOC 2 Type 1 compliance, effective March 28, 2024. That is a useful security checkpoint, but it does not answer questions about current audit coverage, data retention, incident response, availability commitments, or your contractual requirements. Ask for current compliance documentation and a service-level agreement before relying on the system for critical workflows.

Adept does not publish usage or seat limits in the pricing check, so teams should confirm rate limits, concurrency, retries, and failure handling with sales. A post in r/singularity describes an agent that perceives the screen and acts through coordinates and keystrokes; comments also raise concerns about phishing and UI behavior. Those are user discussions, not production guarantees. If your workflow depends on screen interaction, clarify how it handles changed layouts, permissions, sensitive actions, and human approval before deployment.