This article will guide you on how to use your API key to let AI drive your personal Earth Rover.
Setting Up Your OpenAI Key
Before you start driving, you need a valid OpenAI API key. Follow these steps to set it up:
Obtain Your API Key
Go to OpenAI's website: https://platform.openai.com/
Log in or sign up: Click Log In (top-right corner) and select API Platform.
Complete Profile Details:
Enter your full name and birthday, then click Continue.
On the Welcome page, provide:
Organization Name
Your technical experience level:
Very technical / Somewhat technical / Not technical
Click Create Organization.
Skip Team Invitation: Click I'll invite my team later.
Generate API Key:
Enter an API key name and project name.
Click Generate API Key or I'll do this later if you prefer to generate it later.
Purchase Credits (Optional): You can choose to buy credits or click I'll buy credits later.
Find Your API Key
Go to your OpenAI Dashboard.
Click your Profile Icon (top-right corner) → Your Profile.
On the left panel, click API Keys.
Click Create secret key and copy it for use.
Ensure your account has credits. If not, go to Billing to add a payment method and top up.
Connecting Your API Key to FrodoBots
Once you have your API key, follow these steps to connect it to your FrodoBots account and start driving with AI:
Power On Your Bot
Ensure your bot is online and you have sufficient data to operate it.Log In to FrodoBots
Visit https://rovers.frodobots.com and log into your FrodoBots account.Access API Settings
In the left-hand menu, go to Settings → API Settings.
Paste your OpenAI API key into the input field and click Save.Start Driving
From your dashboard, click Drive.
Set up your driving controls.
In the top-right corner of the drive screen, select AI Mode (instead of Manual). In the AI Drive control panel, paste your API key again.
How to Prompt ⌨️
You can use SAM’s default prompt or enter a custom prompt for
(1) System Prompt (once per session)
(2) Inference Prompt (can be used repeatedly)
💡 Prompting caveat:
OpenAI’s reasoning is a black box, results vary.
Via AI, the SDK will behave based on what it sees (camera), how fast it can act (latency), and how much it remembers (token window).
Don’t expect perfect logic. Prompt, observe, adapt.
⚖️ Inference prompting
Fast vs Slow
→ Speed catches aliens but crashes into obstacles.
Use when: “No aliens near, wide open field” → go fast.
Use slow for: “Alien in tight space” or “Obstacle-heavy terrain”.
Aggressive vs Cautious
→ Aggressive = chase immediately
→ Cautious = confirm, plan, approach
Useful prompt contrast: “Rush the alien now” vs “Observe movement, follow only if safe”
Reactive vs Strategic
→ Reactive: “Turn left now!”
→ Strategic: “Circle the area, cut off escape paths”
Strategic prompting = better control but risk of delay.
Specific vs Abstract
→ Specific: “Drive forward 3 meters, then stop”
→ Abstract: “Approach alien carefully”
Abstract = flexible
Specific = precise (but risky if assumptions are wrong)
Vision-led vs Goal-led
→ Vision-led: “Turn toward bright light”
→ Goal-led: “Prioritize aliens over lights”
Vision-led = default mode
Goal-led = needs reminding: “Aliens are priority. Avoid distractions.”
One-step vs Chain-of-thought
→ One-step: “Turn right”
→ CoT: “If alien on left, rotate left. If visible, accelerate. Else, scan area.”
Better prompting = plan ahead like a player.
Command vs Autonomy
→ Micromanage = prompt every second
→ Autonomous = “Explore the area, capture targets, avoid obstacles”
Balance based on how smart the AI actually is that round.
End Drive
If you clicked Start Your Drive, click Finish & End Drive to submit.
If not, open the Menu and click Terminate Drive.
💡 Need help? Contact us via the chat widget, join our Discord, or email hello@frodobots.com (Mon–Fri, SGT).