Free Kimi Temp Number to Receive SMS Online

Use a free virtual number or temp number to receive SMS online from Kimi and, where Kimi accepts public or virtual numbers, to sign up for a Kimi account without paying for the number. You can also compare paid one-time and private options when you need more control. This page currently displays 10 public message records from the available MyTempSMS snapshot. Public messages are visible to everyone; number availability, Kimi acceptance, verification, and delivery are not guaranteed. MyTempSMS is independent from Kimi.

Free public number

$0
  • Public messages are visible
  • Used by multiple visitors
  • No registration required
  • Best for low-priority testing
View free numbers

Private rental

Choose a country

Check price
  • Continued private access
  • Exclusive private number
  • Renew or cancel anytime
  • Choose the rental period in checkout
View rental options

Choose the right option

FeatureFree public numberOne-time verificationPrivate rental
Best forTesting or low priorityQuick verificationFrequent or long-term use
Cost$0Varies by countryVaries by country
Number typeSharedSingle usePrivate
Message visibilityPublicOrder-specificPrivate
ReusabilityMultiple visitorsSingle useDuring rental
Active durationWhile availableUntil verified or expiredSelected rental period
Delivery guaranteeNot guaranteedNot guaranteedNot guaranteed
Setup timeInstantAt checkoutAt checkout

Recent public activity

These are the latest public Kimi messages. They are visible to everyone and may no longer be valid.

View all public numbers
ServiceNumberMessageTime
Kimi
93262546
[Kimi] 987887 is your Kimi verification code for login.
Kimi
7576163138
[Kimi] 387176 is your Kimi verification code for login.

Public numbers are shared and may already be used by other visitors.

Receive Kimi SMS online for AI authentication: phone or email verification codes

Load one free public number before the AI-account prompt and record whether the request targets phone or email. Kimi says verification codes may go to a phone or email; if one does not arrive, verify the destination, wait briefly, then use Resend. Anchor the check to the AI-account prompt you initiated and use timing to distinguish that event from other visible traffic.

Check the AI request during AI authentication against phone or email verification codes

Load one free public number before the AI-account prompt and record whether the request targets phone or email. Kimi says verification codes may go to a phone or email; if one does not arrive, verify the destination, wait briefly, then use Resend. Anchor the check to the AI-account prompt you initiated and use timing to distinguish that event from other visible traffic.

Keep supported regions with VoIP and landline exclusions separate from public SMS delivery on the AI account

Kimi says only phone numbers from supported regions are accepted for this verification context, and it explicitly excludes VoIP numbers and landlines. Use the published supported regions with VoIP and landline exclusions condition as the AI account checkpoint in AI authentication; the public inbox only shows transport.

Let Open Platform password sign-in by phone or account name determine the next step for the AI account

For Kimi Open Platform, a password can be used with either a phone number or an account name after a password has been set. Use the documented Open Platform password sign-in by phone or account name option for the AI account during AI authentication; delivery cannot replace the configured factor.

Resolve replacement-phone restrictions across Kimi services through the service flow for the AI account

When changing the phone number on Kimi Open Platform, the replacement number must not already be registered on Kimi Open Platform or Kimi Assistant. Within AI authentication, keep the service condition for replacement-phone restrictions across Kimi services separate from delivery on the AI account; the outcomes answer different questions.

The AI account depends on ownership-checked account transfer when sign-in is lost, not just message arrival

If the original sign-in method is unavailable, Kimi directs the user to support for an ownership-checked account transfer instead of using a new public number. The public feed may help inspect a message, but it should not become the durable ownership factor for an AI account with saved data.

No expected message in AI authentication: check phone or email verification codes

If a Kimi code is missing, confirm whether the prompt is sending to phone or email and verify the displayed destination before using Resend. Kimi says verification codes may go to a phone or email; if one does not arrive, verify the destination, wait briefly, then use Resend.

Blocked AI authentication step: review supported regions with VoIP and landline exclusions

If Kimi rejects the destination, check supported-region, VoIP, landline, and existing-account restrictions before doing anything else. Kimi says only phone numbers from supported regions are accepted for this verification context, and it explicitly excludes VoIP numbers and landlines.

Recover the existing AI account through ownership-checked account transfer when sign-in is lost

If Kimi loses the original sign-in method, use its ownership-checked transfer or support process rather than a newly selected public number. If the original sign-in method is unavailable, Kimi directs the user to support for an ownership-checked account transfer instead of using a new public number.

Project questions

What context should I use to identify the Kimi message I requested?

Load one free public number before the AI-account prompt and record whether the request targets phone or email. Anchor the check to the AI-account prompt you initiated and use timing to distinguish that event from other visible traffic.

Why should a Kimi account keep long-term recovery off this public feed?

The public feed may help inspect a message, but it should not become the durable ownership factor for an AI account with saved data. For AI authentication, future recovery belongs on a private factor.

AI authentication: is there guidance for phone or email verification codes?

Kimi says verification codes may go to a phone or email; if one does not arrive, verify the destination, wait briefly, then use Resend. This matters for AI authentication.

AI authentication: can supported regions with VoIP and landline exclusions change verification?

Kimi says only phone numbers from supported regions are accepted for this verification context, and it explicitly excludes VoIP numbers and landlines. This matters for AI authentication.

AI authentication: what effect does Open Platform password sign-in by phone or account name have?

For Kimi Open Platform, a password can be used with either a phone number or an account name after a password has been set. This matters for AI authentication.

AI authentication: where does replacement-phone restrictions across Kimi services fit into security?

When changing the phone number on Kimi Open Platform, the replacement number must not already be registered on Kimi Open Platform or Kimi Assistant. This matters for AI authentication.

AI authentication: what does Kimi say about ownership-checked account transfer when sign-in is lost?

If the original sign-in method is unavailable, Kimi directs the user to support for an ownership-checked account transfer instead of using a new public number.

AI authentication: which rule applies to irreversible account deletion and stored data?

Kimi's consumer app provides an account-deletion workflow, and approved deletion is irreversible for associated conversations, files, memory data, and paid benefits. This matters for AI authentication.

Content review date:

Loading