SmartLocator
The intelligence behind every check

Every address is different.
Your AI should be too.

Meet two distinct approaches to address verification: Swift for efficient everyday workloads, and Apex for cases that may need a deeper look.

Explore the models For developers
Built around your workflow Clear speed–depth trade-off

Model selection

Match the model to the task

Concept preview

Swift

Standard

An efficient route for routine checks and larger volumes.

Efficiency focus

Apex

Advanced

More room for reasoning when an address is harder to interpret.

Depth focus

Illustrative comparison only—not live performance data or a model selector.

Routine volume — keep work moving
Complex cases — look a little deeper
Your workflow — choose with intent

Two models. Two strengths.

Choose your approach.

Both are designed for the same goal—helping you assess address quality before dispatch. The difference is where each approach puts its emphasis.

Standard

Swift

Fast. Efficient. Reliable.

Your everyday workhorse for address verification—built around an efficiency-first approach for routine checks and larger batches.

Where Swift fits

  • High-volume workflows
    Process routine checks with efficiency in mind.
  • Familiar address patterns
    Handle common formats and everyday variations.
  • Cost-aware processing
    A practical default for regular workloads.

A good fit when

You need to review many addresses and want an efficiency-focused starting point.

Advanced reasoning

Apex

Deeper reasoning. More insight.

An advanced approach intended for cases where an address is ambiguous, incomplete, or harder to interpret from the information provided.

Where Apex fits

  • Ambiguous details
    Give difficult or unclear address patterns more scrutiny.
  • Multiple clues to interpret
    Reason through the information supplied in the address.
  • Depth over minimum latency
    Allow for potentially longer processing on harder cases.

A good fit when

A case deserves a closer look and the extra processing time may be worthwhile.

Availability note: Swift and Apex are being introduced as planned options. Model selection and final credit usage are not active through this page yet.

View current plans

A clear trade-off

Speed or depth?
Choose deliberately.

There is no universal winner. Swift is positioned for efficient routine work; Apex is intended for cases that may benefit from deeper reasoning. More analysis can require more time, and neither approach can guarantee a correct result for every address.

Decision factorSwiftApex
Core approachEfficiency-first verificationDeeper reasoning for complex cases
Typical useRoutine checks and bulk workloadsAmbiguous or difficult address details
Time expectationDesigned with efficient processing in mindMay take longer depending on the case
Credit usageFinal usage to be confirmed at launchFinal usage to be confirmed at launch
Default recommendation Everyday starting pointChoose when extra analysis may help

This table describes intended positioning, not a benchmark. Actual speed, cost, and outcomes must be measured against representative address data before launch.

Designed for real workflows

From address input to a better-informed decision.

The model is one part of the process. Useful verification also depends on the quality of the input, the checks applied, and how your team acts on the result.

Step 01

Provide the address

Start with the address information available to your business. Clear, complete inputs give the verification process more to work with.

Step 02

Apply the right approach

Use an efficiency-focused approach for routine workloads, or an advanced reasoning approach when the address needs closer interpretation.

Step 03

Review the result

Use verification output as decision support. Review uncertain or high-impact cases instead of treating an AI result as an absolute guarantee.

Made for practical choices

Which one fits your day?

Use these examples as a starting guide—not a rule. Your address mix and operational needs should determine the best fit.

Daily order batches

Reviewing a high volume of mostly familiar shipping addresses.

Start with Swift

Incomplete details

An address contains missing landmarks, unclear locality details, or unusual formatting.

Consider Apex

Automated pipelines

Running repeatable checks through a bulk workflow or API integration.

Start with Swift

Cases needing review

An address looks inconsistent and deserves additional interpretation.

Consider Apex

Questions, answered

Know before you choose.

A quick guide to the intended differences between the two model options.

Still have questions? Contact us
What is the main difference between Swift and Apex?

Swift is positioned for efficient everyday and high-volume verification. Apex is intended for more difficult cases that may benefit from deeper reasoning. The right choice depends on the address and the workflow.

Will Apex take longer?

It may take longer because the intended trade-off favours additional reasoning over minimum latency. Actual timing depends on implementation, workload, and the individual request; comparative timings will need to be measured.

Will Apex cost more credits?

Final credit usage has not been announced on this page. Any pricing difference should be confirmed against actual model costs and shown clearly before the option becomes available.

Does advanced reasoning guarantee a correct address?

No. Additional reasoning can help interpret difficult input, but it cannot guarantee correctness or replace reliable evidence. Treat results as decision support and review uncertain cases.

Can I select a model right now?

Not from this page. Swift and Apex are being presented ahead of the model-selection implementation. The existing product workflow remains separate until that feature is released.

Smarter address workflows

Make every verification count.

Explore SmartLocator today. Swift and Apex model selection will be introduced separately when the feature is ready.

Get started Explore API docs