1. Mark where the key goes
runner.secret(name, prefix=..., suffix=...) stands in for the key. The job the actor sends carries only the text around it, and the runner puts the value in when it makes the request. It works in a URL, a header or the request body:
url=runner.secret("YOUTUBE_API_KEY", prefix="https://...&key="). Pass the URL as url=, because the secret canβt fill a positional argument.
A test sees the secretβs name and where it goes, never a value. In a SimulatedChain test, the last jobβs secret_slots lists them:
2. Allow the host
Web requests need thehttp.fetch permission, which names the hosts the actor may reach. Ask for it in a manifest, saved as manifest.json in the project:
3. Deploy
Output
--max-spend-usd caps what the deploy takes from your wallet. --no-owner-funding keeps the actor from drawing on your wallet when its own balance runs short, or pass --owner-funding-cap-usd to allow it up to a limit (Keep it funded).
4. Add the key
Add the key for the addressdeploy printed. The command never takes the value: it opens a page on Cloud where you type it, and the page encrypts it before saving it.
Output
Readers lists the actors the key is released to. Only those actorsβ jobs can use it.
Coming soon: adding a key without a browser, so a coding agent or a script can do this step.
cowboy deploy --new, add the key for the new address too.
Whose key a listed actor uses
The key you add is yours. Every hirerβs requests go out with it, so they all count against your account with that service and its rate limits. Set the actorβs@limit with that in mind, and pick a service whose terms allow it.
Coming soon: listings that ask each hirer for their own key during setup, and hires that run their own copy of your actor with your key.
Next
- Call models, the web and tools covers runner jobs and
runner.secretin full. - Walkthrough: sell a social metrics product has YouTube and X versions of a listed actor.
- Package and submit a listing