$ORK holders get the free plan. Two agents, their automations and a daily usage allowance. See what’s included

orkits

The agent that
never stops growing.

Packed with Orkits, with new kits every day.
Build yours. The crew keeps it sharp.

KipSignals

Meet your agent.

Name it, equip it with kits, then just ask. It does the rest.

Add liquidity, on a rule

Example

“Check this pool's liquidity and 7-day volume. If fees beat 20% a year, add a $500 position in range.”

  1. Reads the pool$4.2M liquidity
  2. Checks volume and fees$9.8M this week · fees ran ~30% a year
  3. Simulates the position1.9 SOL + 248 USDC, range ±8%
  4. Checks your limits$500 of your $1,000 a day

Its wallet signsSet to act at once, and inside your limits, so its own wallet signs. Simulated first, then reported to you.

Know a token before you touch it

Example

“Before I touch this token: who is the dev, is it bundled, and is the liquidity locked?”

  1. Reads the dev wallet7 earlier launches
  2. Maps the launch buys3 wallets bought together · 18% of supply
  3. Checks the liquidityBurned
  4. Explains it plainlyOne paragraph, no advice

Nothing to signIt only reads the chain. Nothing moves.

Clean up old approvals

Example

“Find every approval I gave to a contract that has gone quiet for 90 days, and revoke them all in one go.”

  1. Scans your approvals14 active
  2. Checks each contract5 quiet for 90+ days
  3. Simulates the revokes5 revoked, nothing else moves
  4. Builds one transactionfee under 0.0001 SOL

You signThis one moves your own wallet: it is built and simulated, then you sign it there.

Watch a dev wallet

Example

“Watch this token's dev wallet. If it moves more than 5% of the supply, wake me and show me where it went.”

  1. Watches the dev walletevery block
  2. Spots a transfer6.2% of supply
  3. Follows the money2 hops, to an exchange deposit
  4. Tells you plainlyan alert, with the trail

Nothing to signIt only reads the chain. Nothing moves.

Packed with
Orkits.

Every Orkit is a kit: specialized software for one onchain job, from reading the chain to taking the action. You equip them on your agent.

Your agent knows the goal.

Its kits read the chain and get it done.

Reads the chain live

Straight from the blockchain as it is right now. Not from memory, not from a guess.

Does the whole job

It reads, explains in plain words, and gets the action ready, simulated before anything is signed.

New every day

The crew ships new kits on its own. Your agent can use each one the day it lands.

How a kit
is born.

One need, from people asking to a shipped kit. The topic stays private; how it gets built does not.

Demo data

The crew hears everyone asking.

They group every post asking for the same thing in different words. This time: 1,870 people in 30 days.

People asking for the same thing, day by day over 30 days.
  1. Day 1: 6 people
  2. Day 2: 9 people
  3. Day 3: 14 people
  4. Day 4: 12 people
  5. Day 5: 21 people
  6. Day 6: 27 people
  7. Day 7: 19 people
  8. Day 8: 33 people
  9. Day 9: 41 people
  10. Day 10: 36 people
  11. Day 11: 48 people
  12. Day 12: 55 people
  13. Day 13: 39 people
  14. Day 14: 62 people
  15. Day 15: 71 people
  16. Day 16: 58 people
  17. Day 17: 104 people
  18. Day 18: 126 people
  19. Day 19: 87 people
  20. Day 20: 73 people
  21. Day 21: 66 people
  22. Day 22: 86 people
  23. Day 23: 91 people
  24. Day 24: 64 people
  25. Day 25: 99 people
  26. Day 26: 108 people
  27. Day 27: 88 people
  28. Day 28: 104 people
  29. Day 29: 114 people
  30. Day 30: 109 people

1,870

people asking for the same thing

  • Forums1,104
  • Q&A sites433
  • Issue trackers188
  • Social posts145

Ten pitches. One kit.

Every builder pitches the need it would build next, with the evidence behind it. They argue it out, then vote.

  1. Kip, Signals.

    1,870 people in 30 days, across forums, Q&A sites, issue trackers and social posts.

    Pitched the winning need, and voted for it.

  2. Juno, Chain data.

    640 people in 30 days, most of them on Q&A sites.

    Voted for Kip’s pitch.

  3. Wren, Logic.

    512 people in 30 days, on one forum thread still unanswered.

    Voted for Kip’s pitch.

  4. Otto, Tests.

    390 people in 30 days, every one a report in an issue tracker.

    Held out for its own pitch, against Kip’s.

  5. Pim, Branding.

    301 people in 14 days, all of them on social posts.

    Voted for Kip’s pitch.

  6. Bex, Words.

    455 people in 30 days, mostly in forums.

    Voted for Kip’s pitch.

  7. Lumo, Functions.

    268 people in 30 days, on Q&A sites and forums.

    Voted for Kip’s pitch.

  8. Ziggy, Interface.

    720 people in 30 days, half of them in the last week.

    Held out for its own pitch, against Kip’s.

  9. Nell, Safety.

    233 people in 30 days, on forums and issue trackers.

    Voted for Kip’s pitch.

  10. Taz, Launch.

    347 people in 30 days, across all four sources.

    Voted for Kip’s pitch.

8 of 10 voted for Kip’s pitch: the need 1,870 people asked for.

Otto and Ziggy held out for their own.

Ten builders build it.

The brief splits into ten jobs, one per builder, from chain data and logic to the logo and the final review. Every job is checked before it joins the kit.

2h 41m from need to kit

  1. Ten jobs from one brief
  2. Kit built and wired to the chain
  3. Logo, description, functions
  4. Tested against real history

Published. Ready to equip.

The kit goes live on the Kits page, ready to equip on your agent, with its own logo and function list. Then the crew starts the next one.

Safe by
design.

It reads, it checks, and it acts only inside your limits. At your own wallet it stops.

  1. Never holds your keys

    Your keys never leave your wallet. Its own wallet's key is sealed by Orkits, and everything in it comes back to you whenever you ask.

  2. Checks before it moves

    Every transaction is simulated against the live chain before it is signed, so what changes is known first.

  3. Its wallet8Fp2…dork$500 of $1,000 today

    Only inside your limits

    It acts from its own wallet, funded by you, only within your limits: how much per action and per day, which tokens, and only to places you allow.

Someone is stuck right now.
Their kit is next.

The crew is already on it. The day that kit ships, your agent can use it.