API tools, one step at a time.
Speconaut starts with knowledge. The direction is a catalog of focused APIs that applications can combine without building a large specialist backend for each tool.
First tool: Speconaut AI
Source-backed questions, comparisons and follow-up context are the first capability. The workspace separates product discovery, source files and Missing review tasks. Source management and customer access retain the boundaries described in the documentation.
Read the API reference or see the v1 release notes. This is an API service layer, not a proprietary foundation-model announcement.
Everything below is planned, not available in v1. These are product directions, not callable endpoints, prices, delivery dates or bundled entitlements.
Image tools
Candidate workflows include preparing product media, transforming images and producing useful image variants. Each tool should specify accepted formats, output dimensions, file limits and how a result is retrieved.
A deterministic resize and an AI-generated image are different operations. Any AI processing, rights requirements or additional charges should be explicit rather than hidden behind a generic upload.
Audio tools
The direction includes speech and audio workflows that an application can request through a small integration. Transcription, speech generation and format processing have different inputs, latency, consent and metering requirements.
Long-running jobs should have status, timeout and result handling. A paid request must not be silently duplicated when a client loses the first response. Exact capabilities and pricing are not announced yet.
File conversion
Conversion tools should turn one documented format into another without forcing every customer to operate a conversion service. The contract needs input validation, output format, size limits and clear handling of unsupported or damaged files.
File conversion is not automatically an AI operation. The billing unit should match the actual work, such as a file, page or processing job, rather than pretending every byte is an AI token.
Document tools
Candidate tasks include extracting content, preparing structured data and helping applications work with documents. The original file, extracted text and a generated summary must remain distinguishable.
Privacy, authorized access, retention, deletion and result quality need review before accepting customer files. A future document tool must not imply that confidential uploads are safe merely because the API request succeeds.
What every tool needs before release
- A clear purpose, documented inputs and verifiable outputs.
- Authenticated access, account ownership and per-tool permissions.
- Understandable usage units, limits and a reviewed cost policy.
- Durable request IDs, safe retries and explicit job states where needed.
- File safety, retention and recovery rules appropriate to the operation.
- Representative quality checks and an honest description of limitations.
The goal is less infrastructure for application teams, not less responsibility for security or consent. Your app still needs a trusted place to keep credentials and decide what its users are allowed to do.
Build around the available contract
Start with the documented knowledge API and its current access policy. Keep planned tools behind your own feature boundaries until their contracts and availability are published. No current account balance or API key promises access to a planned tool.
Questions about an integration can go to Speconaut support. Suggestions do not automatically schedule a feature or authorize a paid background job.