Missing tool request
Tell us the job we still do not close.
The goal is not to inflate a route counter. A useful request describes a real input → output job, the privacy boundary, and why the current catalog or workflows are not enough. No signup form is required.
Search first
Try the catalog, Magic finder, collections and role paths. The best new route is often no new route at all — just better discovery.
Describe input → output
Name the actual file, text, numbers or structured data you start with and the exact result you need back.
State the boundary
Say whether browser-local execution matters and whether the request is syntax, preparation, estimation or something that requires specialist validation.
Request template
A request we can actually evaluate.
Job I need to finish:
Example input or format (do not email secrets or sensitive data):
Expected output:
Why existing tools do not close the job:
Should it run entirely in the browser? Why?
Useful open-source engine or standard, if known:
Is this a one-off utility or a repeat workflow?Privacy + scope
Do not send sensitive payloads in a tool request.
Use synthetic or redacted examples. A request is product feedback, not a secure upload channel, compliance submission or support guarantee. Solarc may decline requests that duplicate an existing route, require unsafe handling, depend on unclear licensing or create a misleading assurance boundary.