zmeyer44

What about an endpoint that references a taproot address and return an array of inscription Ids that the address holds? Perhaps /address-inscriptions/[address] since just /address/[address] it a bit to general...

For the sat recursive endpoint, I think it makes sense to have seperate endpoints for the sat details and the inscriptions associated with a sat. Perhaps `/sat/[satNumber]` just returns information...

Part of me thinks the /content/ is too general and should be further abstracted to ensure it is never accidentially replaced. Why not something like [^content] or just [^in] (abbreviation...

Thanks for the heads up. It's probably something related to the relay cache being used. I'll take a look