API, finance and operations teams · no signup
API reference-field preflight
Check common country, currency and timestamp fields before sending a sample payload or mapping downstream.
Validate representative field values independently so reference-code mistakes are caught before they become integration debugging. This is syntax/reference checking, not end-to-end API validation.
The builder stores route slugs only. It does not carry pasted text, uploaded files or generated results between tool pages.
Outcome-first sequence
The order is curated around the job, not around a product feature menu.
Explicit data boundary
Each atomic tool keeps its own runtime and privacy truth. A recipe never silently moves your payload.
Canonical tools only
Every step resolves against the live free-tool catalog, so stale recipe routes fail closed in code.
Recipe · 3 verified steps
- 1Open step
Check country code
ISO 3166-1 Alpha-2 Country Code Validator
Validate a representative two-letter country code before mapping geography fields.
Validation utilities · validator.js · MIT
- 2Open step
Check currency code
ISO 4217 Currency Code Validator
Validate the three-letter currency value used by the payload or export.
Business utilities · validator.js · MIT
- 3Open step
Check timestamp
RFC 3339 Date & Time Validator
Validate the sample date-time syntax before handing it to another service.
Validation utilities · validator.js · MIT
When the job repeats
Keep one-off work free. Escalate only when repetition creates value.
If this becomes a recurring workflow that needs monitoring, evidence, team controls or support, compare the paid workflow products instead of paying to unlock the atomic utilities.
Pass the useful route forward
Share this workflow, not visitor data.
Native share sends only this canonical Solarc route plus public page context. It never includes tool inputs, generated results, uploaded files, local presets or builder state.