Sandbox API Asks

For a team that size and a TSB product owner who gives it their full attention, how long do you think it’ll take that team to develop the API?

1 Like

It’s exciting to see the start of API layers… :rocket: this will be very helpful for any world building tools @Cyril :rocket:

1 Like

Let’s get this whipped up into a SIP, huh?

Who wants to author it? :eyes:

Anyone who isn’t a delegate wanna take the steering wheel here? :thinking:

Start with documenting all of the data point shared above and making a clear ask.

I can take this one. I started building it as of today and I’ll put the Google doc here for everyone to comment on before I submit it

3 Likes

super cool. API layer will be very useful for some of the tooling we are starting to think about building…

1 Like

As we discussed earlier, it depends. A simple API might take a week, but building an entire platform is a different story—especially if it’s being handled by an internal team at a large company.

Let’s assume 2–3 months, which is usually the minimum time it takes to build something decent :wink:

2 Likes

Quick update on this:

Our UGC Searcher platform will use some of the current APIs provided by the Sandbox. While it won’t have the full complexity that could be reached with more advanced tools, we believe it’ll be enough to demonstrate a strong use case for the kinds of platforms that can be built with this tech. :saluting_face:

4 Likes

Thank you! :slightly_smiling_face:

Is there any way to get a list of those API modules or components that I can include in the API SIP?

I think what I’m going to do is build the SIP that partners with a community member through my own RFP process

1 Like

Yes, but only once they’re implemented. In any case, we won’t be sharing them publicly since that could overwhelm the system with too many requests. :folded_hands:

1 Like

What does “once they’re implemented” mean? I’m building the SIP right now with every API request feature that has been discussed thus far. And when I post the SIP draft here in the next week or so, I’m sure more will be requested.

I don’t understand what is meant when you say overwhelm the system with requests.

Given the unclear state of Sandbox’s current revenue model, it’s likely that the API has been held back as it could become a major future revenue stream.

However, if Sandbox truly wants to transition into an open metaverse, making APIs accessible is a critical milestone. Right now, we’re still operating within a closed metaverse framework.

That said, the new 0.12 update — especially the improved saved variables — suggests the team may be preparing to release limited API access soon.

This could be a turning point. Whether or not APIs are opened will determine if Sandbox evolves into a true platform for builders.

3 Likes

Shont, can you help me understand what you mean by the API can become a major future revenue stream? What does that mean?

1 Like

Why APIs Can Become a Revenue Stream for The Sandbox

:small_blue_diamond: A. Standard Monetization Model in UGC/Game Platforms

Many leading UGC and gaming platforms monetize APIs as a core part of their infrastructure:

  • Roblox offers Roblox Cloud APIs that enable external studios and services to build on their ecosystem. While some APIs are free, advanced tools and integrations often come with restrictions or enterprise pricing.
  • Epic Games provides Epic Online Services (EOS) which are free up to a point, but enterprise-level usage typically involves licensing deals.
  • Unity exposes Unity Cloud APIs that support monetized usage depending on the tier and the level of access.

:backhand_index_pointing_right: The Sandbox could adopt a similar model, monetizing access to real-time game data, player stats, experience tracking, and builder tools.


:small_blue_diamond: B. Examples of API Monetization Models

Model Description Application to Sandbox
Tiered Pricing Charge based on usage (e.g., calls per month) Leaderboards, player analytics, or metadata tools
Paid API Keys Free for basic use; paid for premium features Access to advanced game or LAND data
Access Based on LAND Ownership Free if you own LAND; paid otherwise Revives LAND utility and incentivizes holding
SAND-based Payments Use SAND tokens to pay for API usage
3 Likes

Nice. Thanks. I didn’t realize that.

also r u a chat gpt bot :slightly_smiling_face: :rofl:

1 Like

GPT helps me with my knowledge :laughing:

1 Like

Nothing wrong with that! I’m happy it’s helping and I’m glad you are here :slightly_smiling_face:

2 Likes

Hello there,

We managed to get an answer from TSB product team re the APIs. I’m posting their comment here:

1. On player and experience data availability:
The focus of the Developer Hub is to enable external developers and creators to build new products integrated with The Sandbox ecosystem.

At this stage, the Developer API provides access to basic profile information linked to the authenticated user:

  • Basic user data
  • Owned LANDs and Assets
  • Avatar details
  • SAND wallet balance (if linked)

As well as public information related to:

  • Public assets
  • Dynamic libraries
  • Collections.

Experience-specific or gameplay data (such as quest progress, high scores, or saved variables) is not currently available and is not on the short-term roadmap. These are longer-term considerations.

2. On expanding Creator API access:
There’s no finalized public access process yet, but we’ve drafted an internal preliminary approval flow

While we aim to eventually open access to the broader community, this first phase is focused on building out the Developer Hub itself, we’re still in the discovery and implementation phase, so we’re not yet ready to scale support more broadly.

That said, we expect this process to evolve based on feedback and available capacity.

3. On supporting DAO-funded or community-driven tools:
Our current development bandwidth is quite limited and scoped around the needs of other Programs.

That being said, we are open to supporting 1 or 2 DAO-funded initiatives as long as they are closely aligned with our current roadmap and priorities.

7 Likes

That feels like a rather thoughtful and positive response from TSB, @Cyril. Thanks for relaying info on this matter!

cc: @Lanzer @shont @Gonzacolo @cryptodiplo

The good news is they can, “support initiatives currently aligned with their priorities”.

Now that we have established that the API is already on the roadmap, and what the data points are that will be made available, what exactly does the community want to see in this API?:red_question_mark:

Keep in mind that the more closely aligned any possible SIP is with their existing plans, the better. Being clear and conservative with the request made through the proposal will increase the likelihood it can be achieved (while continuing to build a strong working relationship between the DAO community and TSB devs).

4 Likes

Thank you for getting us this update @Cyril

Yeah I zeroed in on this as well @theKuntaMC . I have no problem scoping the SIP to this.

@Gonzacolo @shont @cryptodiplo @PickaxeMaster what are y’all’s thoughts on what could be “aligned with their priorities” ?

2 Likes