For reference, the TILTX instructions are posted here:
http://vicidial.org/docs/TILTX_SHAKEN_API.txtAs for the container entry, the instructions say "place only the TILTX API key into the Container Entry", so you should place only the TILTX API key into the Container Entry, nothing else. The Container Type doesn't matter, so I will make sure to add that to the instructions. It's hard to show any example which is only a key, without showing an actual key, which is why we didn't show an example in the documentation, since it clearly states "place only the TILTX API key into the Container Entry".
As for TILTX's disconnected number service, do you subscribe to that service with TILTX?(you have to request it, and pay extra for it) If not, it won't do anything, and if you do subscribe to that service, it does not guarantee that you won't ever get disconnected numbers, they have said it is about 90-95% accurate.
As for "Why does it seem like some calls are going into different locations in the database?" I really don't know what you mean here. You list two database tables but don't describe exactly what the issue is in any detail.
The "vicidial_tiltx_shaken_log" table stores the results received from the TILTX API requests, while the "vicidial_urls" table is actually linked to the "vicidial_url_log" table, and it's contents are designed to be viewed in the "Reports -> Admin Utilities -> URL Log Report" report page.