Registered access

Request a StreetKit site ID

Registered sites get better soft rate limits and customer-specific meta URLs for normal StreetKit browser integrations.

This is not an account, paywall, API key, or secret. It is a public label that helps StreetKit classify real integrations and provide support.

Why site IDs exist

A public label for real StreetKit integrations

Site IDs help separate demo or low-volume traffic from real production sites without adding accounts, billing, or hard authentication to public StreetKit access.

Better soft limits

Registered sites get better soft rate limits than public and unidentified traffic, while still using StreetKit's public address data.

Customer-specific access path

A registered site uses a public site ID in its StreetKit setup so traffic can be labelled and supported without adding a login.

Not hard auth

A siteId can be copied from browser code. It is used for soft rate limits and support, not hard authentication.

Public and registered usage

Choose the right endpoint for the job

Public endpoint

Demos and low-volume use

Public access stays available for demos, evaluation, hobby projects, and low-volume community use. It uses stricter soft limits and does not require a siteId.

https://index.streetkit.smp.kiwi/public/v1/meta.json

Registered endpoint

Real sites with better limits

Registered browser integrations use a public siteId and a customer-specific access path. The widget can then label normal address lookup traffic for that integration.

https://index.streetkit.smp.kiwi/c/{siteId}/v1/meta.json

For current soft-limit guidance, browser IP behavior, and future protected access notes, see StreetKit rate limits.

Commercial options

Need stronger support or a private setup?

A normal site ID is enough for many public browser integrations. If you need a more formal commercial arrangement, tell us what you are trying to run and we can discuss the right option.

SLA and support

Commercial support, response expectations, and SLA terms may be possible for teams that need clearer operating commitments.

Private hosted implementation

StreetKit may be available as a private hosted implementation for organisations that need more control over how it is operated.

Local setup help

We can discuss helping you get StreetKit running on your own local system or internal environment where that makes sense.

For commercial requests, email hello@smp.kiwi with your use case, traffic expectations, support needs, and any local/private hosting requirements.

Setup guides

Check the right setup before requesting

These pages explain the current browser-widget paths and beta integration boundaries before you request a site ID.

NZ address autocomplete

Use this for normal forms, checkouts, onboarding, and internal tools.

Webflow address autocomplete

Use this when a Webflow form can load custom code and stable field IDs.

WooCommerce address autocomplete

Review the beta plugin status and checkout limitations before requesting checkout access.

Request details

Tell us where StreetKit will be used

Keep it simple: a domain, a contact, and enough context to check that the integration fits StreetKit's public site ID model. Do not include passwords, API keys, customer records, order details, or private form submissions.

Website or domain Contact email Organisation or project Expected traffic Integration mode

Use case Notes

By submitting, you confirm this request does not include secrets, customer records, order details, or unrelated form data. StreetKit will use these details only to review and operate the site ID request.

Loading verification...

Checking the request form...

If the form is unavailable, email hello@smp.kiwi with the same details and we can process the request manually.

Registered widget example

Sample registered widget snippet

After a siteId is issued, configure the widget with the public siteId and the matching registered access path.

StreetKit.init({
  input: "#address",
  siteId: "sk_live_example",
  indexBaseUrl: "https://index.streetkit.smp.kiwi/c/sk_live_example/v1"
});

Security model

Public identifier, not authentication

siteId is public

A StreetKit siteId is public and browser-visible. It is not authentication, a password, an API key, a bearer token, or proof of site ownership.

Soft limits only

Registered access improves traffic classification. It does not provide login, domain validation, billing-grade quotas, or private data access.

Future protected access

Higher-volume or stricter commercial use may later move to a protected access option with clearer approval, limits, and support terms.

Manual processing

What happens after a request

StreetKit v1 siteId requests are reviewed manually. Real customer registry records stay outside public site content.

Review the requested site, use case, traffic estimate, and integration mode.
Issue a valid public siteId that contains no customer names, emails, or secrets.
Publish the registered access path and send integration instructions.